Methods and systems of operating computing device

ABSTRACT

In one or more embodiments, a system can configure a physical mobile device via configuring a configuration for an emulator of the physical mobile device. For example, a user (e.g., a customer) can request a physical mobile device, and a system can provide the user with an emulation of the physical mobile device, where the user can configure the emulation of the physical mobile device. In one or more embodiments, the user can be provided with the configuration via at least one of a network and a physical delivery of the physical mobile device, configured with the configuration. In one example, the user can execute an emulation of the physical mobile device configured with the configuration, received via the network. In another example, the physical mobile device can be configured with the configuration, and subsequently, the physical mobile device can be physically delivered to the user.

PRIORITY CLAIM

This application claims priority to U.S. Provisional Application Ser.No. 61/905,608, filed 18 Nov. 2013, titled “METHODS AND SYSTEMS OFOPERATING COMPUTING DEVICE”. Each of U.S. Provisional Application Ser.No. 61/905,608, filed 18 Nov. 2013, titled “METHODS AND SYSTEMS OFOPERATING COMPUTING DEVICE”, U.S. application Ser. No. 13/601,537, filed31 Aug. 2013, titled “Methods and Systems of Providing Items to aCustomer Via a Network”, U.S. application Ser. No. 13/428,128, filed 23Mar. 2012, titled “Methods And Systems Of Providing Items To CustomersVia a Network”, and U.S. Provisional Application Ser. No. 61/627,349,filed 11 Oct. 2011, titled “Methods and Systems of Providing Items toCustomers via a Network” is hereby incorporated by reference in itsentirety as though fully and completely set forth herein.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is related to the following commonly assigned,co-pending U.S. patent application(s) filed on even date herewith, withall content incorporated herein by reference:

U.S. patent application Ser. No. 14/5646,922, titled “Methods andSystems of Operating Computing Device.”

BACKGROUND

1. Technical Field

This disclosure relates generally to the field of assisting users inconfiguring computing devices.

2. Description of the Related Art

In the past, users of computing devices read manuals, watchedinstructional videos, and/or received help from customer servicerepresentatives to learn how to configure their computing devices. Inone example, these manuals and videos are often difficult for some, ifnot most, users to utilize in configuring their computing devices. Inanother example, help from customer service representatives often cannotbe referred to at a later time (e.g., after receiving help from customerservice representatives). This can pose issues of customer satisfactionand/or additional cost in providing customer service representatives.

Moreover, in the past, a user/customer could order a mobile device, suchas a wireless telephone, and would have to wait until the mobile devicewas physically delivered to the user/customer before the user/customercould configure the mobile device. For example, the user/customer wouldhave to wait until physical delivery of the mobile device beforepurchasing applications (APPs), arranging application (APP) icons to bedisplayed via the mobile device, configuring an address book APP,configuring a weather APP, and/or configuring an electronic mail APP,among others.

BRIEF DESCRIPTION OF THE DRAWINGS

The preferred embodiments will become apparent upon reading thefollowing detailed description and upon reference to the accompanyingdrawings in which:

FIG. 1 provides an exemplary block diagram of a network communicationssystem, according to one or more embodiments;

FIG. 2A provides an exemplary block diagram of a hardware and softwarestack of a computing device, according to one or more embodiments;

FIGS. 2B-2F provide exemplary block diagrams of a computing device,according to one or more embodiments;

FIG. 3A illustrates an exemplary client interface, according to one ormore embodiments;

FIG. 3B provides an exemplary method of an application walk-through,according to one or more embodiments;

FIG. 3C provides another exemplary method of an applicationwalk-through, according to one or more embodiments;

FIG. 3D provides an exemplary method of operating an applicationmanager, according to one or more embodiments;

FIG. 4A provides a conceptual illustration of a transparent layer over auser interface, according to one or more embodiments;

FIGS. 4B and 4C provide conceptual illustrations of a transparent layerwith a beacon over a user interface, according to one or moreembodiments;

FIG. 4D provides a conceptual illustration of a transparent layer with auser selecting an area of a user interface indicated by a beacon,according to one or more embodiments;

FIG. 4E provides an illustration of a computing device with a userselecting an area of a user interface indicated by a beacon, accordingto one or more embodiments;

FIG. 4F provides an illustration of a media interface with a pointingdevice selecting an area of a user interface indicated by a beacon,according to one or more embodiments;

FIG. 4G provides an illustration of a first application that indicatesan action to be performed via a second application, according to one ormore embodiments;

FIG. 4H provides a conceptual illustration of a transparent layer of afirst application that indicates an action to be performed via a secondapplication, according to one or more embodiments;

FIG. 4I provides another illustration of a first application thatindicates an action to be performed via a second application, accordingto one or more embodiments;

FIG. 4J provides an illustration of a first application that indicates aswipe action to be performed via a second application, according to oneor more embodiments;

FIGS. 5A-5G provide exemplary diagrams of ordering and configuring acomputing device, according to one or more embodiments;

FIG. 5H illustrates an exemplary diagram of delivering a mobile deviceconfiguration, according to one or more embodiments;

FIGS. 5I and 5J illustrate exemplary diagrams of a wearable computingdevice, according to one or more embodiments;

FIG. 5K illustrates a method of creating a configuration of a computingdevice and delivering the configuration is illustrated, according to oneor more embodiments;

FIGS. 6A-6C provide exemplary diagrams of a simulated object, accordingto one or more embodiments;

FIG. 6D illustrates an exemplary diagram of a simulated object withoperational aids, according to one or more embodiments;

FIG. 6E illustrates an exemplary system that supports physical deviceemulation, according to one or more embodiments;

FIG. 6F provides an exemplary method of operating an applicationprogramming interface server application, according to one or moreembodiments;

FIG. 6G provides an exemplary method of operating a server application,according to one or more embodiments;

FIG. 6H provides an exemplary method of operating an emulator serverapplication, according to one or more embodiments;

FIG. 6I provides an exemplary method of operating a client that caninteract with an emulator, according to one or more embodiments;

FIG. 6J provides an exemplary method of providing multiple simulatedobjects to multiple customer computing devices, according to one or moreembodiments;

FIG. 7A illustrates an exemplary mobile device that emulates a physicaldevice, according to one or more embodiments;

FIG. 7B illustrates an exemplary mobile device that emulates a physicaldevice, where a transparent layer with a beacon over a user interfacedirects user input, according to one or more embodiments;

FIGS. 7C and 7D provide exemplary diagrams of a computing device,according to one or more embodiments;

FIGS. 8-10 illustrate exemplary network systems that supports storage ofdata and configurations of physical mobile devices, according to one ormore embodiments;

FIGS. 11-13 illustrate exemplary network systems that support recoveryand/or restoration of data and configurations of physical mobiledevices, according to one or more embodiments;

FIG. 14 illustrates an exemplary system that supports installation ofdata and configurations of one or more physical mobile devices to one ormore respective emulators, according to one or more embodiments;

FIGS. 15-17 illustrate exemplary local area network systems that supportstorage of data and configurations of physical mobile devices, accordingto one or more embodiments;

FIGS. 18-20 illustrate exemplary local network systems that supportrecovery and/or restoration of data and configurations of physicalmobile devices, according to one or more embodiments;

FIGS. 21 and 22 illustrate exemplary systems that support storage ofdata and configurations of physical mobile devices, according to one ormore embodiments;

FIG. 23 illustrates an exemplary local network system that supportsinstallation of data and configurations and utilization of an emulator,according to one or more embodiments;

FIG. 24 illustrates an exemplary system that supports installation ofdata and configurations and utilization of multiple emulators, accordingto one or more embodiments;

FIG. 25 illustrates an exemplary computing system, according to one ormore embodiments;

FIG. 26 provides an exemplary method of a computer system receiving andstoring mobile device data, according to one or more embodiments;

FIG. 27 provides an exemplary method of a mobile device receiving andstoring mobile device data, according to one or more embodiments;

FIG. 28 provides an exemplary method of transforming telecommunicationssignals, according to one or more embodiments;

FIG. 29 provides another exemplary method of transformingtelecommunications signals, according to one or more embodiments;

FIG. 30 provides an exemplary method of utilizing an emulator, accordingto one or more embodiments;

FIG. 31 provides another exemplary method of utilizing an emulator,according to one or more embodiments;

FIGS. 32 and 33 illustrate exemplary block diagrams of emulators coupledtogether, according to one or more embodiments; and

FIG. 34 provides an exemplary method of emulating two or more coupledmobile devices, according to one or more embodiments.

While one or more embodiments may be susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and will herein be described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to limit the disclosure to theparticular form disclosed, but on the contrary, the disclosure is tocover all modifications, equivalents and alternatives falling within thespirit and scope of this disclosure.

DETAILED DESCRIPTION

In one or more embodiments, a system can configure a physical mobiledevice via configuring a configuration for an emulator of the physicalmobile device. For example, a user (e.g., a customer) can request aphysical mobile device, and a system can provide the user with anemulation of the physical mobile device, where the user can configurethe emulation of the physical mobile device. In one or more embodiments,the user can be provided with the configuration via at least one of anetwork and a physical delivery of the physical mobile device,configured with the configuration. In one example, the user can executean emulation of the physical mobile device configured with theconfiguration, received via the network. In another example, thephysical mobile device can be configured with the configuration, andsubsequently, the physical mobile device can be physically delivered tothe user.

In one or more embodiments, a user/customer can utilize a first mobiledevice and shop for a second mobile device that will be utilized withthe first mobile device. For example, the first mobile device can be orinclude one or more of a wireless telephone, a personal digitalassistant, and a digital music player, among others, and the secondmobile device can be or include a watch (e.g., a smart watch), amongothers. In one or more embodiments, the first and second physical mobiledevices can be emulated. For example, the first and second physicalmobile devices can be emulated to configure the second mobile device. Inone instance, an emulated coupling of the first mobile device with thesecond mobile device can include a wireless emulated coupling. Inanother instance, an emulated coupling of the first mobile device withthe second mobile device can include a wired emulated coupling. Afterthe second mobile device is configured, a configuration of the secondmobile device can be provided to the user via a network, and/or thesecond mobile device, configured with the configuration, can be providedto the user via a physical delivery service, according to one or moreembodiments.

In one or more embodiments, a user can be provided with a walk-throughand/or tutorial that can be utilized to configure a mobile device. Forexample, a first application can provide a walk-through and/or tutorialof a second application. In one or more embodiments, the firstapplication can implement a conceptual transparent layer of a display ofthe mobile device, where the first application can provide messagesand/or can indicate actions that could and/or should be taken by a user.In one example, the first application can provide messages to configurea mail application. In another example, the first application canprovide an indication that a “swipe” can be performed with a secondapplication. For instance, the swipe can reveal additional informationprovided by the second application and/or change displayed information.

Turning now to FIG. 1, a block diagram of a network communication systemis illustrated, according to one or more embodiments. As illustrated,one or more customer computing devices (CCDs) 1110-1114 can be coupledto a network 1010. In one or more embodiments, network 1010 can includeone or more of a wireless network and a wired network. Network 1010 canbe coupled to one or more types of communications networks, such as oneor more of a public switched telephone network (PSTN), a public widearea network (e.g., an Internet), a private wide area network, and alocal area network, among others. In one example, network 1010 can be orinclude an Internet. In another example, network 1010 can form part ofan Internet. In one or more embodiments, one or more of CCDs 1110-1114can be coupled to network 1010 via a wired communication coupling and/ora wireless communication coupling. In one example, a customer computerdevice (CCD) can be coupled to network 1010 via wired Ethernet, a DSL(digital subscriber loop) modem, or a cable (television) modem, amongothers. In another example, a CCD can be coupled to network 1010 viawireless Ethernet (e.g., WiFi), a satellite communication coupling, acellular telephone coupling, or WiMax, among others.

As shown, one or more media servers 1210-1212 can be coupled to network1010, and media servers 1210-1212 can include media server interfaces1220-1222, respectively. As illustrated, media servers 1210 and 1211 canbe coupled to databases 1230 and 1231, and media server 1212 can includea database (DB) 1232. In one example, DB 1230 can be or include anOracle database. In a second example, DB 1231 can be or include aMicrosoft SQL Server database. In another example, DB 1232 can be orinclude a MySQL database or a PostgreSQL database.

In one or more embodiments, one or more of media server interfaces1220-1222 can provide one or more computer system interfaces to one ormore of CCDs 1110-1114. In one example, media server interface 1220 caninclude a web server. In another example, media server interface 1221can include a server that interacts with a client application of a CCD.In one instance, the client application can include a “smart phone”application. In a second instance, the client application can include atablet computing device application. In another instance, the clientapplication can include a computing device application (e.g., anapplication for a desktop or laptop computing device).

As illustrated, one or more customer service devices (CSDs) 1310-1312can be coupled to network 1010. In one or more embodiments, a servicerepresentative (e.g., a customer service representative of a retailestablishment, a service representative of a service provider, etc.) canutilize a customer service device (CSD) to interact with a customerutilizing a CCD. For example, the service representative can utilize theCSD to provide information to the customer via the CCD. In one instance,the service representative can utilize the CSD to conduct one or more ofa video chat, a text chat, and an audio chat. In a second instance, theservice representative can utilize the CSD to illustrate and/ordemonstrate one or more features and/or operations of an object for saleor of an object for which service is desired by the customer.

Turning now to FIG. 2A, an exemplary block diagram of a hardware andsoftware stack of a computing device is illustrated, according to one ormore embodiments. As shown, hardware 2110 can interface with a kernel2210 that can interface with an application (APP) manager 2310. Asillustrated, applications (APPs) can interface with APP manager 2310. Inone or more embodiments, APP manager 2310 can include a window managerthat can provide and/or implement an application programming interface(API) of and/or for a graphical user interface (GUI) framework.

As shown, hardware 2110 can include one or more of a processor 2010, amemory medium 2117, a display 2120, a touch screen 2130, a button 2140,a button 2142, a button 2144, a transceiver 2150 (e.g., a wirelessEthernet transceiver, a WiFi transceiver, etc.), a transceiver 2152(e.g., a wireless telephone transceiver, a cellular telephone networktransceiver, a satellite telephone network transceiver, etc.), and aserial interface 2160 (e.g., a universal serial bus (USB) interface, aFireWire interface, a wired Ethernet interface, a RS-232 interface, aThunderbolt interface, etc.), among others. As illustrated, kernel 2210can include one or more of a display driver (DRV) 2220, a touch screenDRV 2230, a button DRV 2240, a transceiver DRV 2250, a transceiver DRV2252, a serial interface DRV 2260, a scheduler 2270, and a queue 2280,among others.

In one or more embodiments, a driver of kernel 2210 can includeinstructions executable by processor 2010 to interface with a hardwareunit of hardware 2110. For example, drivers 2220-2260 can respectivelyinclude instructions executable by processor 2010 to interface withrespective hardware units 2120-2160. In one or more embodiments, one ormore of drivers 2220-2260 can provide data to queue 2280. In oneexample, touch screen DRV 2230 can provide data associated with one ormore of coordinates, a hold, and a swipe, among others, of touch screen2230 to queue 2280. In another example, button DRV 2240 can provide dataassociated with an actuation of one or more of buttons 2140-2144 toqueue 2280. In one or more embodiments, queue 2280 can include one ormore queues. For example, queue 2280 can include one or more of an eventqueue and a work queue, among others.

In one or more embodiments, scheduler 2270 can schedule time thatprocesses and/or threads can utilize a processor unit. For example,scheduler 2270 can schedule time that one or more of kernel 2210, APPmanager 2310, and APPs 2420-2426 can utilize processor 2010.

In one or more embodiments, scheduler 2270 can dequeue data from queue2280 and provide the dequeued data to APP manager 2310. For example, thedata dequeued from queue 2280 can be queued in queue 2380. In oneinstance, data associated with one or more of coordinates, a hold, and aswipe, among others, of touch screen 2230 can be queued in queue 2380.In another instance, data associated with an actuation of one or more ofbuttons 2140-2144 can be queued in queue 2380.

In one or more embodiments, scheduler 2270 can process work of a workqueue of queue 2280. For example, a driver of kernel 2210 can queue workin queue 2280, and scheduler 2270 can process work queued in queue 2280.For instance, work in queue 2280 can include first data and acorresponding first function (e.g., a subroutine) that processes thefirst data.

In one or more embodiments, APP manager 2310 can provide data to one ormore of APPs 2420-2426. For example, APP manager 2310 can provide eventdata to one or more of APPs 2420-2426. In one or more embodiments, APPmanager 2310 can retrieve data from kernel 2210 via a file system 2280of kernel 2210. For example, APP manager 2310 can access one or morepseudo files (e.g., “device files”, files in /dev, files in /dev/input,files in /proc, etc.) to retrieve and/or obtain data that can beprovided to one or more of APPs 2420-2426.

In one or more embodiments, APP manager 2310 can implement and/ormaintain identifications (IDs) associated with respective APPs. In oneexample, APP manager 2310 can implement and/or maintain first dataassociated with a first APP via a first APP identification (ID). Inanother example, APP manager 2310 can implement and/or maintain seconddata associated with a second APP via a second APP ID.

In one or more embodiments, APP manager 2310 can implement and/ormaintain callbacks associated with respective APPs. In one example, afirst APP can register a first callback (e.g., instructions executableby processor 2010) with APP manager 2310, and APP manager 2310 canexecute the first callback with first data, associated with the firstAPP, as parameter passed to the first callback. In a second example, asecond APP can register a second callback (e.g., instructions executableby processor 2010) with APP manager 2310, and APP manager 2310 canexecute the second callback with second data, associated with the secondAPP, as parameter passed to the second callback. In another example,data queued in queue 2380 can be provided to one or more APPs via one ormore respective callbacks. In one instance, one or more of coordinates,a hold, and a swipe, among others, of touch screen 2230 can be providedto an APP via its callback(s). In another instance, data associated withan actuation of one or more of buttons 2140-2144 can be provided to anAPP via its callback(s).

Turning now to FIG. 2B, an exemplary computing device is illustrated,according to one or more embodiments. As shown, a computing device (CD)2000 can include one or more of processor 2010 and one or more of memorymedium 2117, display 2120, touch screen 2130, button 2140, button 2142,button 2146, transceiver 2150, transceiver 2152, and serial interface2160, among others, coupled to processor 2010. As illustrated, memorymedium 2117 can include and/or store one or more of kernel 2210, APPmanager 2310, APP 2420, APP 2422, APP 2424, and APP 2426, among others,which can be executed by processor 2010. In one or more embodiments,computing device 2000 can be or include a computer, a computer system, aworkstation, a mobile device, a mobile computing device, a hand-heldcomputing device, a personal digital assistant (PDA), a cellulartelephone, a tablet computing device, a digital music player device, awireless telephone, a satellite telephone, a virtual computing device(e.g., a virtual machine), an in-vehicle computing device (e.g., anin-vehicle entertainment system, an in-vehicle navigation system, anin-vehicle configuration and/or status system), and an automotivecomputing device, among others. In one or more embodiments, CD 2000illustrated in FIGS. 2B-2F can be utilized to implement a CCD and/or aCSD.

Turning now to FIG. 2C, a computing device is illustrated, according toone or more embodiments. As shown, CD 2000 can include processor 2010coupled to a memory medium 2020. In one or more embodiments, memorymedium 2020 can store data and/or instructions that can be executed byprocessor 2010. For example, memory medium 2020 can store one or moreAPPs 2030-2032 and/or an operation system (OS) 2035. For instance, oneor more APPs 2030-2032 and/or an OS 2035 can include instructions of aninstruction set architecture (ISA) associated with processor 2010. Inone or more embodiments, CD 2000 can be coupled to and/or include one ormore of a display, a keyboard, and a pointing device (e.g., a mouse, atrack ball, a track pad, a stylus, etc.). In one or more embodiments, atouch screen can function as a pointing device. In one example, thetouch screen can determine a position via one or more pressure sensors.In another example, the touch screen can determine a position via one ormore capacitive sensors.

As illustrated, CD 2000 can include one or more network interfaces 2040and 2041. In one example, network interface 2040 can interface with awired network coupling, such as a wired Ethernet, a T-1, a DSL modem, aPSTN, or a cable modem, among others. In another example, networkinterface 2041 can interface with a wireless network coupling, such as asatellite telephone system, a cellular telephone system, WiMax, WiFi, orwireless Ethernet, among others.

In one or more embodiments, CD 2000 can be any of various types ofdevices, including a computer system, a server computer system, a laptopcomputer system, a notebook computing device, a portable computer, aPDA, a handheld mobile computing device, a mobile wireless telephone(e.g., a satellite telephone, a cellular telephone, etc.), an Internetappliance, a television device, a DVD (digital video disc player)device, a Blu-Ray disc player device, a DVR (digital video recorder)device, a wearable computing device, or other wireless or wired devicethat includes a processor that executes instructions from a memorymedium. In one or more embodiments, processor 2010 can include one ormore cores. For example, each core of processor 2010 can implement anISA. In one instance, two or more cores of processor 2010 can implementa same ISA. In another instance, two or more cores of processor 2010 canimplement different instruction set architectures (ISAs). In one or moreembodiments, one or more of CCDs 1110-1114, media servers 1210-1212,databases 1230 and 1231, and CSDs 1310-1312 can include one or more sameor similar structures and/or functionalities described with reference toCD 2000.

Turning now to FIG. 2D, a computing device is illustrated, according toone or more embodiments. As shown, CD 2000 can include a fieldprogrammable gate array (FPGA) 2012 coupled to memory medium 2020. Inone or more embodiments, memory medium 2020 can store data and/orconfiguration information that can be utilized by FPGA 2012 inimplementing one or more systems, methods, and/or processes describedherein. For example, memory medium 2020 can store a configuration (CFG)2033, and CFG 2033 can include configuration information and/or one ormore instructions that can be utilized by FPGA 2012 to implement one ormore systems, methods, and/or processes described herein. For instance,the configuration information and/or the one or more instructions, ofCFG 2033, can include a hardware description language and/or a schematicdesign that can be utilized by FPGA 2012 to implement one or moresystems, methods, and/or processes described herein. In one or moreembodiments, FPGA 2012 can include multiple programmable logiccomponents that can be configured and coupled to one another inimplementing one or more systems, methods, and/or processes describedherein.

In one or more embodiments, memory medium 2020 can store data and/orinstructions that can be executed by FPGA 2012. For example, memorymedium 2020 can store one or more APPs 2030-2032 and/or an OS 2035. Forinstance, one or more APPs 2030-2032 and/or an OS 2035 can includeinstructions of an ISA associated with FPGA 2012. In one or moreembodiments, CD 2000 can be coupled to and/or include one or more of adisplay, a keyboard, and a pointing device (e.g., a mouse, a track ball,a track pad, a stylus, etc.). In one or more embodiments, a touch screencan function as a pointing device. In one example, the touch screen candetermine a position via one or more pressure sensors. In anotherexample, the touch screen can determine a position via one or morecapacitive sensors.

As illustrated, CD 2000 can include one or more network interfaces 2040and 2041. In one example, network interface 2040 can interface with awired network coupling, such as a wired Ethernet, a T-1, a DSL modem, aPSTN, or a cable modem, among others. In another example, networkinterface 2041 can interface with a wireless network coupling, such as asatellite telephone system, a cellular telephone system, WiMax, WiFi, orwireless Ethernet, among others.

In one or more embodiments, CD 2000 can be any of various types ofdevices, including a computer system, a server computer system, a laptopcomputer system, a notebook computing device, a portable computer, aPDA, a handheld mobile computing device, a mobile wireless telephone(e.g., a satellite telephone, a cellular telephone, etc.), an Internetappliance, a television device, a DVD device, a Blu-Ray disc playerdevice, a DVR device, a wearable computing device, or other wireless orwired device that includes a FPGA that processes data according to oneor more methods and/or processes described herein. In one or moreembodiments, one or more of CCDs 1110-1114, media servers 1210-1212,databases 1230 and 1231, and CSDs 1310-1312 can include one or more sameor similar structures and/or functionalities described with reference toCD 2000.

Turning now to FIG. 2E, a computing device is illustrated, according toone or more embodiments. As shown, CD 2000 can include an applicationspecific processor (ASIC) 2014 coupled to memory medium 2020. In one ormore embodiments, memory medium 2020 can store data and/or configurationinformation that can be utilized by ASIC 2014 in implementing one ormore systems, methods, and/or processes described herein. For example,memory medium 2020 can store a CFG 2034, and CFG 2034 can includeconfiguration information and/or one or more instructions that can beutilized by ASIC 2014 to implement one or more systems, methods, and/orprocesses described herein.

In one or more embodiments, memory medium 2020 can store data and/orinstructions that can be executed by ASIC 2014. For example, memorymedium 2020 can store one or more APPs 2030-2032 and/or an OS 2035. Forinstance, one or more APPs 2030-2032 and/or an OS 2035 can includeinstructions of an ISA associated with ASIC 2014. In one or moreembodiments, CD 2000 can be coupled to and/or include one or more of adisplay, a keyboard, and a pointing device (e.g., a mouse, a track ball,a track pad, a stylus, etc.). In one or more embodiments, a touch screencan function as a pointing device. In one example, the touch screen candetermine a position via one or more pressure sensors. In anotherexample, the touch screen can determine a position via one or morecapacitive sensors.

As illustrated, CD 2000 can include one or more network interfaces 2040and 2041. In one example, network interface 2040 can interface with awired network coupling, such as a wired Ethernet, a T-1, a DSL modem, aPSTN, or a cable modem, among others. In another example, networkinterface 2041 can interface with a wireless network coupling, such as asatellite telephone system, a cellular telephone system, WiMax, WiFi, orwireless Ethernet, among others.

In one or more embodiments, CD 2000 can be any of various types ofdevices, including a computer system, a server computer system, a laptopcomputer system, a notebook computing device, a portable computer, aPDA, a handheld mobile computing device, a mobile wireless telephone(e.g., a satellite telephone, a cellular telephone, etc.), an Internetappliance, a television device, a DVD device, a Blu-Ray disc playerdevice, a DVR device, a wearable computing device, or other wireless orwired device that includes ASIC that processes data according to one ormore methods and/or processes described herein. In one or moreembodiments, one or more of CCDs 1110-1114, media servers 1210-1212,databases 1230 and 1231, and CSDs 1310-1312 can include one or more sameor similar structures and/or functionalities described with reference toCD 2000.

Turning now to FIG. 2F, a computing device is illustrated, according toone or more embodiments. As shown, CD 2000 can include graphicsprocessing unit (GPU) 2016 coupled to memory medium 2020. For example,GPU 2016 can be or include a general purpose graphics processing unit(GPGPU). In one or more embodiments, memory medium 2020 can store dataand/or configuration information that can be utilized by GPU 2016 inimplementing one or more systems, methods, and/or processes describedherein. For example, memory medium 2020 can store a CFG 2036, and CFG2036 can include configuration information and/or one or moreinstructions that can be utilized by GPU 2016 to implement one or moresystems, methods, and/or processes described herein.

In one or more embodiments, memory medium 2020 can store data and/orinstructions that can be executed by GPU 2016. For example, memorymedium 2020 can store one or more APPs 2030-2032 and/or an OS 2035. Forinstance, one or more APPs 2030-2032 and/or an OS 2035 can includeinstructions of an ISA associated with GPU 2016. In one or moreembodiments, CD 2000 can be coupled to and/or include one or more of adisplay, a keyboard, and a pointing device (e.g., a mouse, a track ball,a track pad, a stylus, etc.). In one or more embodiments, a touch screencan function as a pointing device. In one example, the touch screen candetermine a position via one or more pressure sensors. In anotherexample, the touch screen can determine a position via one or morecapacitive sensors.

As illustrated, CD 2000 can include one or more network interfaces 2040and 2041. In one example, network interface 2040 can interface with awired network coupling, such as a wired Ethernet, a T-1, a DSL modem, aPSTN, or a cable modem, among others. In another example, networkinterface 2041 can interface with a wireless network coupling, such as asatellite telephone system, a cellular telephone system, WiMax, WiFi, orwireless Ethernet, among others.

In one or more embodiments, CD 2000 can be any of various types ofdevices, including a computer system, a server computer system, a laptopcomputer system, a notebook computing device, a portable computer, aPDA, a handheld mobile computing device, a mobile wireless telephone(e.g., a satellite telephone, a cellular telephone, etc.), an Internetappliance, a television device, a DVD device, a Blu-Ray disc playerdevice, a DVR device, a wearable computing device, or other wireless orwired device that includes a GPU that processes data according to one ormore methods and/or processes described herein. In one or moreembodiments, one or more of CCDs 1110-1114, media servers 1210-1212,databases 1230 and 1231, and CSDs 1310-1312 can include one or more sameor similar structures and/or functionalities described with reference toCD 2000.

Turning now to FIG. 3A, an exemplary client interface is illustrated,according to one or more embodiments. As shown, a display 3000 candisplay a client interface 3020. In one or more embodiments, display3000 can be coupled to or included in a computing device. In oneexample, display 3000 can be coupled to CCD 1111. In another example,display 3000 can be included in CCD 1112. In one or more embodiments,client interface 3020 can be or include a web browser (e.g., MicrosoftInternet Explorer, Safari, Firefox, Chrome, Opera, etc.), a window of anapplication, a full screen display area of display 3000, or a partialscreen display area of display 3000. For example, client interface 3020can be utilized by APP 2030 to provide information to and/or receiveuser input from a user. In one or more embodiments, an APP (e.g., an APPof APPs 2030-2032) can receive information from a media server (e.g., amedia server of media servers 1210-1212) via a network (e.g., network1010) and can provide the information to a user via client interface3020.

In one or more embodiments, the APP (e.g., the APP of APPs 2030-2032)can be or include a plug-in to another application (e.g., a web browser)and/or can receive configuration information from a media server. In oneexample, the plug-in can include a Flash Player (available from AdobeSystems), and the plug-in can interface with the customer via clientinterface 3030. In another example, the plug-in can include a Javavirtual machine, and the plug-in can interface with the customer viaclient interface 3030. In one or more embodiments, client interface 3030can be implemented via one or more of JavaScript, EMCAScript, Java, anextensible markup language (XML), and a hypertext markup language (HTML)(e.g., HTML version four (4), HTML version five (5), etc.). For example,the APP (e.g., the APP of APPs 2030-2032) can be or include a webbrowser, and the web browser can receive information, from a mediaserver, that includes one or more of JavaScript, EMCAScript, Java (e.g.,Java byte code), XML, and HTML version 5, and the web browser canimplement client interface 3020 based on the received information thatincludes one or more of JavaScript, EMCAScript, Java, XML, and HTMLversion 5.

As illustrated, client interface 3020 can include an interactive mediainterface 3030 that can provide information to a customer (e.g., a userof a CCD) and/or receive information from a customer. In one example,interactive media interface 3030 can include a media interface 3040 thatcan display one or more pictures, one or more videos (e.g., motionpictures), one or more graphics, and/or text associated with an object3050. In one instance, object 3050 can represent and/or include asimulation of an object for sale by a retail establishment. In a secondinstance, object 3050 can provide and/or implement an emulation of anobject (e.g., an emulation of a physical mobile device, a physicalcomputing device, etc.). In another instance, object 3050 can representand/or include a simulation of an object that can be serviced and/or forwhich service can be provided. In a second example, interactive mediainterface 3030 can include an interactive communication interface 3060that can be utilized by one or more of the customer and another user(e.g., a sales representative, a service representing, a representativeof a retail establishment, a representative of a service provider, anartificial intelligence system, a neural network system, etc.).

In another example, interactive media interface 3030 can include one ormore icons or button 3110-3117 that can be provided to receive userinput. In one or more embodiments, object 3050 can include arepresentation of and/or a simulation of a device, a computer, acellular telephone, a tablet computing device, a digital music playerdevice, a satellite telephone, a dress, a pair of jeans, a bathing suit,a shoe, lingerie, underwear, a helmet, a sock, stockings, a watch, anecklace, a bracelet, a television, software (e.g., a drawing program, aword processing program, a music player program, a compiler, a computeroperating system, a video editing program, etc.), a printer device, atire, a rim, an automobile part, an automobile, a piece of furniture, ora stapler, among others.

In one or more embodiments, one or more of icons 3110-3113 can beselected by the customer to change a viewing angle of object 3050. Inone example, icon 3110 can be selected to rotate object 3050 about afirst axis by a number of degrees in a first direction of rotation withrespect to the first axis. In a second example, icon 3111 can beselected to rotate object 3050 about the first axis by a number ofdegrees in a second direction of rotation with respect to the firstaxis. For instance, the second direction of rotation can be opposite tothe first direction of rotation. In a third example, icon 3112 can beselected to rotate object 3050 about a second axis by a number ofdegrees in a third direction of rotation with respect to the secondaxis. In another example, icon 3113 can be selected to rotate object3050 about the second axis by a number of degrees in a fourth directionof rotation with respect to the second axis. For instance, the fourthdirection of rotation can be opposite to the third direction ofrotation. In one or more embodiments, a pointer can be dragged acrossmedia interface 3040 to rotate object 3050 in a direction about an axis.

In one or more embodiments, icon 3114 can be selected to display a videothat includes and/or is associated with object 3050. For example, icon3114 can be selected to display an interactive video that includesand/or is associated with object 3050. For instance, media interface3040 can display a simulation that includes and/or is associated withobject 3050. In one or more embodiments, icon 3115 can be selected toreceive information about and/or associated with object 3050. In oneexample, interactive communication interface 3060 can provide thecustomer with information when icon 3115 is actuated or selected. In oneinstance, an avatar (e.g., a graphical approximation and/or rendering ofan actual person or a simulated person) can be displayed, viainteractive communication interface 3060, that can provide the customerwith information. In another instance, interactive communicationinterface 3060 can provide the customer with a video of a servicerepresentative. For example, a customer service representative caninteract with the customer directly via text chat and/or video chat viainteractive communication interface 3060.

In one or more embodiments, a customer service representative caninteract with a customer directly by controlling media interface 3040via a media server (e.g., a media server of media servers 1210-1212).For example, the customer service representative can, via a mediaserver, rotate object 3050 about an axis, zoom in-on at least a portionof object 3050, zoom out-from object 3050, start a simulation of orassociated with object 3050, or start a video of or associated withobject 3050, among others. For instance, media server 1210 can receivecontrol information from the customer service representative, via a CSD,and can provide the control information to APP 2030 via network 1010,and APP 2030 can perform, via interactive media interface 3030 and/ormedia interface 3040, one or more functions associated with the controlinformation.

In one or more embodiments, audio information (e.g., speech, music,etc.) can be provided to the customer via a sound output device includedin or coupled to a computing device utilized by the customer. In oneexample, CCD 1110 can include a speaker, and speech from a customerservice representative can be provided to the customer via the speaker.In a second example, CCD 1110 can include a speaker, and speechassociated with object 3050 can be provided to the customer via thespeaker. In another example, CCD 1110 can include a speaker, and musicassociated with object 3050 can be provided to the customer via thespeaker.

In one or more embodiments, icons 3116 and 3117 can be selected toadjust a size of object 3050. In one example, icon 3116 can be selectedto increase a size of object 3050. For instance, increasing a size ofobject 3050 can include zooming in-on object 3050 and/or magnifying atleast a portion of object 3050. In another example, icon 3117 can beselected to decrease a size of object 3050. For instance, decreasing asize of object 3050 can include zooming out-from object 3050.

In one or more embodiments, a first APP can provide an application-basedtutorial that can walk a user through steps to use a second APP of acomputing device (e.g., CD 2000). For example, the first APP can utilizeone or more beacons as a transparent-layer APP to highlight intendedaction and/or motion of the user interaction with the computing device,and when the user interacts with the computing device (either a physicalimplementation or a virtual implementation, such as a virtual machineimplementation), the user action (e.g., user input) is provided to thefirst APP via a transparent layer and then to an interface manager(e.g., a window manager, an APP manager, etc.) and/or the second APP. Inone instance, the user action (e.g., user input) can be provided to thefirst APP via a transparent layer 4550 (illustrated in FIG. 4A), and thefirst APP can provide the user action a window manager and/or the secondAPP. In another instance, the first APP can utilize a visual beacon 4620(illustrated in FIG. 4B) within transparent layer 4550 to highlightand/or signal an intended action and/or a motion of the user interactionwith the computing device.

In one or more embodiments, if the user moves a location of an APP iconsuch that a beacon would be in an incorrect location, the first APP canbe configured to attain and/or procure coordinates of APP icons suchthat one or more beacons can be provided at respective appropriate oneor more areas within a transparent layer. For example, the first APP canattain and/or procure coordinates of APP icons 4610-4614 (illustrated inFIG. 4A) such that one or more beacons (e.g., one or more visualsignals) can be provided at respective appropriate one or more areaswithin transparent layer 4550. For instance, the first APP can attainand/or procure coordinates of APP icons 4610-4614 during aninitialization phase and/or a start-up sequence of its execution.

Turning now to FIG. 3B, an exemplary method of an applicationwalk-through is illustrated, according to one or more embodiments. At3210, a first APP can start. In starting the first APP, the first APPcan attain and/or procure coordinates of APP icons during aninitialization phase and/or a start-up sequence of its execution,according to one or more embodiments. At 3220, the first APP canindicate a user action. In one example, the first APP can indicate auser action via a beacon (e.g., a visual signal), such as a beacon 4620(illustrated in FIG. 4B). For instance, beacon 4620 can indicate thatthe user action should include selecting APP icon 4610. In anotherexample, the first APP can indicate via a swipe indicator 4424(illustrated in FIG. 4J) that the user should and/or could swipe thedisplay.

In one or more embodiments, an APP icon can be moved during use of acomputing device. For example, APP icon 4610 could have been moved froma first location to a second location during use of the computing device(illustrated in FIGS. 4B and 4C), and the first APP can indicate a useraction via beacon 4620 (illustrated in FIG. 4C). In one instance, thefirst APP can attain and/or procure, via a data structure stored in thecomputing device, coordinates of APP icon 4610 during an initializationphase and/or a start-up sequence of its execution. In another instance,the first APP can attain and/or procure, via a data structure stored inthe computing device, coordinates of APP icon 4610 prior to indicatingthe user action via beacon 4610.

At 3230, the first APP can receive user input. For example, the firstAPP can receive the user input via transparent layer 4550, asillustrated in FIG. 4D. For instance, transparent layer 4550 can be aconceptual transparent layer its purposes and/or functionality describedherein. In one or more embodiments, the first APP can receive the userinput via a portion of the user and/or a pointing device. In oneexample, the first APP can receive the user input via a portion of theuser, such as a digit. For instance, the first APP can receive the userinput via a finger 4710, as illustrated in FIGS. 4D and 4E. In anotherexample, the first APP can receive the user input via one or more of amouse, a stylus, a trackball, and a touchpad, among others. Forinstance, CD 2000 can be or include a virtual machine, and the user caninterface with CD 2000 via a media interface 6542 (e.g., a web browser),illustrated in FIG. 4F, where the user can utilize one or more of amouse, a stylus, a trackball, and a touchpad, among others, to positiona pointer 4752 to select APP icon 4610, indicated via beacon 4620. Inone or more embodiments, media interface 6542 can include one or morefunctionalities and/or structures as media interface 3040.

In one or more embodiments, the first APP can filter user input. Forexample, the first APP can receive user input via a portion oftransparent layer 4550 that includes (a) beacon 4620 and/or (b) an areathat includes beacon 4620 and an area around beacon 4620, and the firstAPP can exclude and/or redact user input outside and/or not included inthose areas. At 3240, the first APP can determine if the user input iswithin an area that includes (a) beacon 4620 and/or (b) an area thatincludes beacon 4620 and an area around beacon 4620.

If the user input is not within the area that includes (a) beacon 4620and/or (b) the area that includes beacon 4620 and the area around beacon4620, the user input can be excluded and/or redacted, at 3250. In one ormore embodiments, excluding and/or redacting the user input can includediscarding the user input.

If the user input is within the area that includes (a) beacon 4620and/or (b) the area that includes beacon 4620 and the area around beacon4620, the first APP can provide the user input to one or more of asecond APP and an interface manager, among others, at 3260. In oneexample, the first APP can provide the user input to an interfacemanager (e.g., a window manager, an APP manager, etc.). For instance,the user input provided to the interface manager can select APP icon4610. In another example, the first APP can provide the user input to asecond APP. For instance, after an APP icon is selected, a second APPcan execute, and the first APP can provide the user input to the secondAPP.

Turning now to FIG. 3C, another exemplary method of an applicationwalk-through is illustrated, according to one or more embodiments. At3310, a first APP can be started. For example, the first APP can be APP2426, and APP 2426 can be started. At 3320, a second APP can be started.For example, the second APP can be an APP of APPs 2420-2424, and the APPof APPs 2420-2424 can be started. In one or more embodiments, the firstAPP can start the second APP.

At 3330, the first APP can indicate an action to be performed via thesecond APP. In one example, the first APP can indicate an action to beperformed via the second APP via a message 4410, as illustrated in FIG.4G. For instance, the second APP can be or include an electronic mail(email) client, and the first APP can indicate to enter an email loginvia input area 4210 of email APP interface 4220, as illustrated in FIG.4G. In another example, the first APP can indicate an action to beperformed via the second APP via indicator 4424, as illustrated in FIG.4J. For instance, indicator 4424 can indicate that the user shouldand/or could swipe the display. For example, additional forecast dayscan be displayed via a weather application interface 4422 when the userswipes in the direction indicated via indicator 4424. In one or moreembodiments, indicator 4424 can be animated. For example, indicator 4424can be animated to indicate that the user should and/or could swipe thedisplay.

As illustrated in FIGS. 4G-4I, display 2120 can display email APPinterface 4120 and a scroll bar 4130, among others. As shown, email APPinterface 4120 can display text input areas 4210-4220 and 4235, checkboxes 4225 and 4230, and buttons and/or icons 4510 and 4512. Asillustrated FIG. 4G, the first APP can display message 4410 via display2120.

With reference again to the method of FIG. 3C, the first APP can receiveuser input, at 3340. For example, the first APP can receive user inputvia touch screen 2130, illustrated in FIGS. 4G, 4I, and 4J. In oneinstance, the user input can include one or more alpha numericcharacters. In another instance, the user input can a swipe.

In one or more embodiments, the first APP can receive the user input viatouch screen 2130. As illustrated in FIG. 4H, the first APP can receivethe user input via shaded area 4550 of touch screen 2130, for example.Shaded area 4550 is for illustrative purposes, and the first APP canreceive the user input via an area, corresponding to shaded area 4550,that can be transparent.

With reference again to the method of FIG. 3C, the first APP candetermine if the user input indicates an exit and/or conclusion of thefirst APP, at 3350. For example, the first APP can determine if the userinput indicates an exit and/or conclusion of the first APP (e.g., anexit and/or conclusion of the walk-through) if the user input indicatesa selection of an exit and/or conclusion icon. For instance, the userinput can indicate a selection of an exit and/or conclusion icon 4810,illustrated in FIGS. 4B, 4C, and 4E-4J.

If the user input indicates an exit and/or conclusion of the first APP,the first APP can exit and/or conclude at 3380. If the user input doesnot indicate an exit and/or conclusion of the first APP, the first APPcan provide the user input to the second APP, at 3360. In one example,the first APP can provide the user input to the second APP via APPmanager 2310. For instance, the first APP can provide the user input toqueue 2380, and APP manager 2310 can provide the user input to thesecond APP. In another example, the first APP can provide the user inputto the second APP via kernel 2210. For instance, the first APP canprovide the user input to queue 2280, and the user input stored in queue2280 can be provided to the second APP via at least one method, system,and process described herein.

At 3370, the first APP can determine if addition user input isapplicable. For example, the first APP can be configured for a number ofscenarios of the second APP. For instance, the first APP can beconfigured to additionally aid a user with configuring one or more oftext input areas 4215, 4220, and 4235 and selecting between check boxes4225 and 4230. If the first APP determines that addition user input isapplicable, the method can proceed to 3330, where the first APP canindicate an action to be performed via the second APP. For example, thefirst APP can indicate an action to be performed via the second APP viamessage 4412, as illustrated in FIG. 4I. For instance, the first APP canindicate to enter a name via input area 4215 of email APP interface4120, as illustrated in FIG. 4I. If the first APP determines thataddition user input is not applicable, the first APP can exit at 3380.For example, the first APP can determine that addition user input is notapplicable via a conclusion of a set-up and/or walk-through process.

Turning now to FIG. 3D, a method of operating an APP manager isillustrated, according to one or more embodiments. At 3410, APP manager2310 can receive data from a first APP. For example, the first APP canbe APP 2426, and APP 2426 can provide the data to APP manager 2310. At3420, APP manager 2310 can store the data from the first APP. Forexample, APP manager 2310 can store the data from the first APP viaqueue 2380.

At 3430, APP manager 2310 can remove focus from the first APP. In one ormore embodiments, “focus” indicates a component of a GUI that isselected to receive input. For example, text pasted from a clipboardand/or entered via a keyboard can be sent to the component that has thefocus. In one or more embodiments, APP manager 2310 withdraws and/orremoves the focus an APP by giving another APP the focus.

At 3440, APP manager 2310 can provide focus to a second APP. Forexample, the second APP can be an APP of APPs 2420-2424. At 3450, APPmanager 2310 can provide, to the second APP, the data received from thefirst APP. In one or more embodiments, APP manager 2310 can provide, tothe second APP, the data received from the first APP via a callback(e.g., a subroutine, a function, a procedure, a subprogram, a method, acallable unit, etc.) of the second APP. For example, APP manager 2310can provide, to the second APP, the data received from the first APP viaan instantiation of the callback of the second APP with the datareceived from the first APP as a parameter of the callback of the secondAPP.

In one or more embodiments, APP manager 2310 can utilize multiplecallbacks of the second APP. In one example, APP manager 2310 canutilize a first callback of the second APP to handle text (e.g., userinput text). In a second example, APP manager 2310 can utilize a secondcallback of the second APP to handle a check or uncheck of a checkbox.In third example, APP manager 2310 can utilize a third callback of thesecond APP to handle movement of a scrollbar. In another example, APPmanager 2310 can utilize a fourth callback of the second APP to handle aswipe of a user interface.

At 3460, APP manager 2310 can remove focus from the second APP. At 3470,APP manager 2310 can provide focus to the first APP. In one or moreembodiments, the first APP can control a second APP via APP manager 2310and the method of FIG. 3D.

As described above, CD 2000 can be or include a virtual machine, and theuser can interface with CD 2000 via media interface 6542 (e.g., a webbrowser), illustrated in FIG. 4F. In one or more embodiments, the firstAPP (described with reference to the walk-throughs) can be or includemedia interface 6542. For example, media interface 6542 can executeinstructions that can implement and/or function as the first APP. Forinstance, media interface 6542 can execute a script (e.g., JavaScript,EMCAScript, etc.) and/or byte code (e.g., Java byte code) that canfunction as the first APP, described with reference to thewalk-throughs. In this fashion, a user can utilize, configure, and/orset-up a mobile device, according to one or more embodiments, asdescribed further below.

Turning now to FIGS. 5A-5G, exemplary diagrams of ordering andconfiguring a computing device are illustrated, according to one or moreembodiments. In one or more embodiments, a user/customer can utilize aCCD to interface with a merchant CD (e.g., an online retailer) and ordera computing device via the merchant CD and a network. For example, asillustrated in FIG. 5A, a user/customer 5010 can utilize CCD 1112 tointerface with a merchant CD 5114 (e.g., an online retailer) and order acomputing device (e.g., CD 2000) via merchant CD 5114 and network 1010.In one or more embodiments, CD 2000 can be any of various types ofdevices, including a computer system, a server computer system, a laptopcomputer system, a notebook computing device, a portable computer, aPDA, a handheld mobile computing device, a mobile wireless telephone(e.g., a satellite telephone, a cellular telephone, etc.), an Internetappliance, a television device, a DVD (digital video disc player)device, a Blu-Ray disc player device, a DVR (digital video recorder)device, an in-vehicle computing device, a wearable computing device(e.g., illustrated in FIGS. 5I and 5J), a watch, a smart watch, or otherwireless or wired device that includes a processor that executesinstructions from a memory medium.

In one or more embodiments, the user/customer can utilize the CCD tointerface with a computer system (CS) and configure a virtual CD (e.g.,a virtual machine) via the network. For example, user/customer 5010 canutilize CCD 1112 to interface with a CS 5210 and configure a virtual CD(e.g., a virtual machine) via network 1010. In one or more embodiments,one or more configurations of one or more respective virtual computingdevices (CDs) can be stored. In one example, CS 5210 can includestorage, and the one or more configurations of the one or morerespective virtual CDs can be stored via the storage included in CS5210. In a second example, storage can be coupled to a network, and theone or more configurations of the one or more respective virtual CDs canbe stored via the storage coupled to the network. In another example, asillustrated in FIG. 5B, a storage 5121 can be coupled to CS 5210, andthe one or more configurations of the one or more respective virtual CDscan be stored via storage 5121.

As shown in FIG. 5B, a CFG 5310 can be stored via storage 5121. In oneor more embodiments, CFG 5310 can include one or more sound recordings(e.g., MP3 songs, musical pieces, voice memos, conversations, lectures,etc.), one or more contacts (e.g., contact information associated withpeople, places, companies, etc.), login information, online accountinformation, one or more bookmarks (e.g., web browser book marks), oneor more ebooks, one or more social networking sites' respectiveinformation (e.g., Facebook information, Twitter information, MySpaceinformation, Foursquare information, Last.fm information, Google+information, etc.) associated with a user of a MD, and/or one or moremobile device apps (e.g., smart phone apps, tablet computer apps, musicplayer apps, in-vehicle apps, etc.), among others.

In one or more embodiments, a retailer, a seller, etc., can provide aphysical CD to a physical deliver service (e.g., a postal service, aparcel service, a courier service, a courier, an in-store pick-up, anautomobile dealership, etc.). For example, as illustrated in FIG. 5C, aretailer, a seller, etc., can provide CD 2000 (e.g., in a physicalembodiment) to a physical deliver service 5115 (e.g., a postal service,a parcel service, a courier service, a courier, an in-store pick-up,etc.). As shown in FIG. 5C, CD 2000 can be stored via warehouse 5140(e.g., a physical warehouse, a physical stockroom, etc.), and CD 2000can be provided to physical delivery service 5115.

In one or more embodiments, providing a physical CD to a physicaldelivery service can include marking packaging of the physical CD. Inone example, packaging of the physical CD can be marked with informationthat can identify one or more of the user and the physical CD. Inanother example, packaging of the physical CD can be marked with addressinformation. For instance, the address information can include aphysical address, associated with user 5010, that is utilizable byphysical deliver service 5115 to deliver the physical CD to user 5010.

In one or more embodiments, the user/customer can receive the physicalCD via a physical deliver service (e.g., a postal service, a parcelservice, a courier service, a courier, an in-store pick-up, etc.). Forexample, as illustrated in FIG. 5D, user/customer 5010 can receive CD2000 via a physical deliver service 5115 (e.g., a postal service, aparcel service, a courier service, a courier, an in-store pick-up, anautomobile dealership, etc.).

In one or more embodiments, a CD, received via a physical deliveryservice, can be coupled to a network, and the CD can receive and/orretrieve a configuration that was configured prior to receiving the CDvia the physical delivery service. For example, as illustrated in FIG.5E, CD 2000 can be coupled to network 1010, and CD 2000 can receiveand/or retrieve CFG 5310. For instance, CS 5210 can retrieve CFG 5310from storage 5121 and can provide CFG 5310 to CD 2000 via network 1010.

In one or more embodiments, a CD can be configured at a place associatedwith a retailer, a seller, etc. For example, as illustrated in FIG. 5F,CD 2000 can be configured at warehouse 5140, and CD 2000 can be providedto physical delivery service 5115 after CD 2000 is configured with CFG5310. In one instance, CD 2000 can be configured with CFG 5310 atwarehouse 5140 in a wireless fashion. In another instance, CD 2000 canbe configured with CFG 5310 at warehouse 5140 in a wired fashion. Asshown in FIG. 5G, physical delivery 5115 can provide CD 2000, configuredwith CFG 5310, to customer/user 5010.

In one or more embodiments, a configuration can be provided to one ormore computing devices. For example, as illustrated in FIG. 5H, CFG 5310can be provided to one or more of CCD 1112 and a mobile device (MD)5510. In one or more embodiments, one or more computing devices canemulate a MD, based on a provided configuration. For example,user/customer 5010 can begin to utilize an emulation of a configured MDvia one or more of CCD 1112 and MD 5510. In one instance, user/customer5010 can begin to utilize an emulation of CD 2000, configured with CFG5310, via CCD 1112 and/or MD 5510 before a physical delivery of CD 2000.In another instance, user/customer 5010 can begin to utilize anemulation of CD 2000, configured with CFG 5310, via CCD 1112 and/or MD5510 without any physical delivery of CD 2000.

Turning now to FIG. 5K, a method of creating a configuration of acomputing device and delivering the configuration is illustrated,according to one or more embodiments. At 5610, a request for a computingdevice can be received. For example, merchant CD 5114 can receive therequest for the computing device. In one instance, the request for thecomputing device can be or include an order for the computing device. Inanother instance, as illustrated in FIG. 5A, a user/customer 5010 canutilize CCD 1112 to interface with a merchant CD 5114 (e.g., an onlineretailer) and order the computing device (e.g., CD 2000) via merchant CD5114 and network 1010. In one or more embodiments, the requested and/orordered computing device can be a physical mobile device.

At 5620, an emulator corresponding to the requested and/or orderedcomputing device can be requested. For example, merchant CD 5114 canrequest the emulator of CS 5210. At 5630, CS 5210 can receive theemulator allocation request. At 5640, the emulator can be allocated. Forexample, an emulator of emulators 6420-6425, illustrated in FIG. 6E, canbe allocated. For instance, the emulator can correspond to a physicalmobile device that includes a physical processor, a physical memory, anda physical integrated circuit.

At 5650, the emulator can emulate the computing device. For example, theemulator can be or include a data processing emulator such as QEMU,SPIM, VMware, VirtualBox, or Bochs, among others. At 5660, data can bereceived via a network. For example, CS 5210 can receive data from user5010 via network 1010.

At 5670, the received data can be provided to the emulator. At 5680 aconfiguration can be created. For example, the received data can beutilized to configure the emulated computing device and/or create aconfiguration (e.g., CFG 5310). For instance, CFG 5310 can include oneor more sound recordings (e.g., MP3 songs, musical pieces, voice memos,conversations, lectures, etc.), one or more contacts (e.g., contactinformation associated with people, places, companies, etc.), one ormore bookmarks (e.g., web browser book marks), one or more ebooks, oneor more social networking sites' respective information (e.g., Facebookinformation, Twitter information, MySpace information, Foursquareinformation, Last.fm information, Google+ information, etc.) associatedwith user 5010, and/or one or more mobile device apps (e.g., smart phoneapps, tablet computer apps, music player apps, in-vehicle apps, etc.),among others, based on and/or created via the received data.

At 5690, the configuration can be stored. In one example, theconfiguration can be stored via storage 5121. In another example, theconfiguration can be stored via one or more of storages 6120-6122,illustrated in FIG. 6E. At 5700, user input indicating a delivery methodcan be received. In one example, CS 5210 can receive the user inputindicating the delivery method. In another example, merchant CD 5114 canreceive the user input indicating the delivery method.

At 5710, a delivery method can be determined. In one example, CS 5210can determine the delivery method. In another example, merchant CD 5114can determine the delivery method. In one or more embodiments, deliveryof the configuration can include one or more of delivering theconfiguration via the network (e.g., network 1010) and delivering aphysical computing device configured with the configuration.

If the delivery of the configuration (e.g., CFG 5310) includesdelivering the configuration via the network (e.g., network 1010), theconfiguration can be provided to the user via the network, at 5720. Forexample, CFG 5310 can be delivered to CCD 1112 and/or to MD 5510 vianetwork 1010, as illustrated in FIG. 5H. If the delivery of theconfiguration (e.g., CFG 5310) includes delivering the physicalcomputing device configured with the configuration, the physicalcomputing device can be configured with the configuration, at 5730, andthe physical computing device (e.g., CD 2000) can be provided to aphysical delivery service, at 5740. For instance, the physical deliveryservice can provide the physical computing device (e.g., CD 2000) asdescribed herein.

Turning now to FIGS. 6A-6C, exemplary diagrams of a simulated object areillustrated, according to one or more embodiments. As shown in FIG. 6A,simulated object 3050 can include one or more of a wireless telephone(e.g., a cellular telephone, a satellite telephone, a wireless Ethernettelephone, etc.), a digital music player, a tablet computing device, anda PDA, among others. As illustrated, object 3050 can include one or moreof a simulated sound output device 6010, a simulated display 6020, andsimulated buttons 6030-6032.

As shown, simulated display 6020 can display one or more of a picture orgraphic 6050 and one or more buttons or icons 6040-6046. In one or moreembodiments, a customer (e.g., a user of a CCD) can select and/oractuate one or more of icons 6040-6046 and buttons 6030-6032, andsimulated object 3050 can perform one or more simulated functionsassociated with a selection or simulation of a selected icon or buttonof object 3050. In one example, the customer can select button 6031, anda numeric keypad can be displayed via simulated display 6020. Forinstance, keys of the numeric keypad can simulate a keypad of atelephone. In a second example, the customer can select button 6032, andan interface to a digital music player can be displayed via simulateddisplay 6020. In another example, an icon of icons 6040-6046 can beselected to simulate a respective application of a calculatorapplication, a clock application, a calendar application, a web browserapplication, a video chat application, a video player (e.g., a motionpicture player) application, and a setting or configuration application.

In one or more embodiments, a simulation of object 3050 and/or one ormore simulated features and/or functions can be performed via a CCD. Inone example, a client-side script (e.g., JavaScript, EMCAScript, etc.)can be executed by a web browser of the CCD. In a second example, acompiled client-side program (e.g., Java byte code) can be executed by aweb browser of the CCD. In one or more embodiments, a simulation ofobject 3050 and/or one or more simulated features and/or functions canbe performed via a media server. In one example, the media server canreceive information from a CCD that indicates a simulated button or iconhas been selected and can utilize simulated display, via media interface3040, to display functionality associated with the selected button oricon.

As shown in FIG. 6B, simulated display 6020 can display a simulation ofa video chat application. In one example, a simulated picture or graphic6141 of a person with whom the customer is chatting can be displayed viasimulated display 6020. In another example, a simulated picture orgraphic 6142 of the customer can be displayed via simulated display6020. For instance, picture or graphic 6142 of the customer candemonstrate a front-facing camera of simulated object 3050. In one ormore embodiments, the simulation of the video chat application can bestarted and/or executed in response to a selection and/or actuation ofbutton or icon 6044 of FIG. 6A. For example, the simulation of the videochat application can be a video (e.g., a motion picture) that can beplayed via simulated display 6020.

In one or more embodiments, simulated display 6020 can be utilized toplay one or more videos (e.g., motion pictures). In one example,simulated display 6020 can be utilized to play a clip from Youtube. In asecond example, simulated display 6020 can be utilized to play a trailerto a movie. In another example, simulated display 6020 can be utilizedto play videos that demonstrate one or more features of simulated object3050. In one or more embodiments, user input can be received to pause,play, rewind, and/or fast-forward the video played via simulated display6020.

In one or more embodiments, the customer can select button 6030 toreturn to a “home” state or location of simulated object 3050. Forexample, the “home” state or location of simulated object 3050 isillustrated in FIG. 6A. As illustrated in FIG. 6C, a picture or graphic6250 can be displayed via simulated display 6020. For example, pictureor graphic 6250 can be included in a graphical advertisement for aphysical device associated with its simulated object 3050.

Turning now to FIG. 6D, an exemplary diagram of a simulated object withoperational aids is illustrated, according to one or more embodiments.As shown in FIG. 6D, media interface 3040 can display where a headphoneor headset connector 6310 can be plugged into a device associated withsimulated object 3050 and/or can display where a USB (universal serialbus) connector 6320 can be plugged into a device associated withsimulated object 3050. In one or more embodiments, a demonstrationand/or simulation of coupling connectors to a device can be automated.

In one example, the customer can select “How to use headphones with yourdevice” from a help menu. For instance, a media server can provide, to amedia interface, data and/or information that includes a demonstrationand/or simulation that demonstrates and/or simulates a process ofcoupling headphones with simulated object 3050. In another example, thecustomer can select “How to charge your device or connect your device toa PC or a Mac” from a help menu. For instance, a media server canprovide, to a media interface, data and/or information that includes ademonstration and/or simulation that demonstrates and/or simulates aprocess of coupling simulated object 3050 with a computing device. Forexample, the demonstration and/or simulation can simulate a process ofcoupling simulated object 3050 with at least one of a PC, a Mac, and acharging device (e.g., a wall charger, a solar charger, etc.).

In one or more embodiments, a demonstration and/or simulation ofconnecting connectors to a device can instantiated and/or coordinated bya service representative via a CSD and/or a media server. For example, aservice representative can be communicating with a customer, viatelephone or via interactive communication interface 3060, and canprovide control information, via one or more of CSD 1310, network 1010,and media server 1212, to interactive communication interface 3060and/or an application associated with interactive communicationinterface 3060. For instance, the service representative can providecontrol information, via one or more of CSD 1310, network 1010, andmedia server 1212, to client interface 3020 and/or an applicationassociated with client interface 3020, and media interface 3040 candisplay a demonstration of connecting headphone or headset connector6310 and/or USB connector to a device associated with simulated object3050.

In one or more embodiments, a simulated object can be an emulatedobject. For example, simulated object 3050 can be an emulation of aphysical device. In one instance, simulated object 3050 can be anemulation of CD 2000. In another instance, simulated object 3050 can bean emulation of CD 2000, and CS 5210 can emulate CD 2000.

Turning now to FIG. 6E, an exemplary system that supports physicaldevice emulation is illustrated, according to one or more embodiments.As shown, one or more of CCDs 1111-1113 can be coupled to CS 5210 vianetwork 1010. In one or more embodiments, CS 5210 can include and/orexecute one or more of a server app 6410, a server APP 6411, a serverAPP 6440, and an API (application programming interface) server APP6450. As illustrated, API server APP 6450 can be coupled to server APP6440, server APP 6440 can be coupled to server APP 6410, and server APP6450 can be coupled to server APP 6411. In one or more embodiments, afirst server APP can be coupled to a second server APP via one or moreof a named pipe, an anonymous pipe, a pipe, a Unix domain socket, anetwork connection (e.g., a network socket connection such as at leastone of TCP, UDP, and IP, among others), a D-Bus (Desktop Bus), an IPC(interprocess communication) (e.g., inter-thread communication,inter-application communication, etc.), a shared memory interface,message passing, a file, and a file system, among others.

As illustrated, server APP 6410 can include one or more of an emulatorproxy 6430 and one or more of emulators 6420-6422, and one or more ofemulators 6420-6422 can be coupled to emulator proxy 6430. As shown,server APP 6411 can include one or more of one or more emulator proxies6433-6435 and one or more of emulators 6423-6425, and one or more ofemulators 6423-6425 can be coupled to respective one or more emulatorproxies 6433-6435. In one or more embodiments, one or more of emulators6423-6425 can include one or more of the same, similar or differentfunctionalities and/or structures described with reference to one ormore emulators 6420-6422, and one or more of emulator proxies 6433-6435can include one or more of the same, similar or differentfunctionalities and/or structures described with reference to emulatorproxy 6430.

In one or more embodiments, one or more of emulator proxy 6430 and oneor more of emulators 6420-6422 can include or be one or more of aprocess, a task, an application, and a thread, among others; and anemulator of emulators 6420-6422 can be coupled to emulator proxy 6430via one or more of a named pipe, an anonymous pipe, a pipe, an Unixdomain socket, a network connection, a D-Bus, an IPC, a shared memoryinterface, message passing, a file, and a file system, among others.

As shown, one or more of CCDs 1111-1113 can include and/or executerespective one or more client interfaces 63021-63023, respective one ormore interactive media interfaces 63031-63033, and/or respective one ormore media interfaces 6541-6543. In one or more embodiments, one or moreclient interfaces 63021-63023 can include same or similar one or morefunctionalities described with reference to client interface 3020, oneor more interactive media interfaces 63031-63033 can include same orsimilar one or more functionalities described with reference tointeractive media interface 3030, and/or one or more media interfaces6541-6543 can include same or similar one or more functionalitiesdescribed with reference to media interface 3040.

As illustrated, one or more of mobile devices (MDs) 6110-6112 can becoupled to CS 5210 via network 1010. As shown, CS 5210 can include astorage 6120, can be coupled to a storage 6121, and/or can be coupled toa storage 6122 via network 1010. In one or more embodiments, one or moreof storages 6120-6122 can include non-volatile storage and/or memorythat can store configurations and/or data of one or more of MDs6110-6112.

In one or more embodiments, CS 5210 and/or storages 6120-6122 canprovide and/or implement one or more system for synchronizing and/orstoring preferences, configuration(s), installed applications of aphysical MD in a system independent format (e.g., the system can be usedfor multiple OS types and/or multiple platform types). In one example,one or more granular levels (e.g., storing and/or retrieving data forrecovery may not require that a recovered system synchronize its data,information, and/or configuration with CS 5210 and/or storages6120-6122) of data (e.g. data such as applications, contact list(s),photos, videos, ring tone(s), sound preference(s), etc.) can be storedand/or retrieved. For instance, an API can be provided and/or madeavailable that can be utilized in storing and retrieving associatedinformation and/or data of and/or associated with one or more physicalmobile devices. In another example, multiple devices can be configuredand/or recovered from CS 5210 and/or storages 6120-6122. In oneinstance, each of the multiple devices can be configured and/orrecovered with respective associated data and/or configuration(s).

In another instance, multiple devices can be configured and/or recoveredfrom CS 5210 and/or storages 6120-6122. For example, each of themultiple devices can be configured and/or recovered with same dataand/or configuration(s). For instance, a company can issue multiplewireless telephones to a sales group, and each of the multiple wirelesstelephones can be configured with one or more of a contact list, salespresentations, and smart phone applications, among others, for the salesgroup.

Turning now to FIG. 6F, an exemplary method of operating an API serverAPP is illustrated, according to one or more embodiments. At 6610, afirst request from a CCD (e.g., a CCD of CCDs 1111-1113) can bereceived. For example, API server APP 6450 included in and/or executedby media server 1211 can receive, via network 1010, the first requestfrom the CCD. In one instance, API server APP 6450 can receive, vianetwork 1010, the first request from media interface 6541 included inand/or executed by CCD 1111. In a second instance, API server APP 6450can receive, via network 1010, the first request from media interface6542 included in and/or executed by CCD 1112. In another instance, APIserver APP 6450 can receive, via network 1010, the first request from aninteractive media interface (e.g., an interactive media interface ofinteractive media interfaces 63031-63033) or a client interface (e.g., aclient interface of client interfaces 63021-63023).

In one or more embodiments, the first request can include a request forconnection information. For example, the first request can include aXMLHttpRequest (XHR) that includes the request for the connectioninformation. At 6620, a second request can be provided to another serverAPP. For example, API server APP 6450 can provide the second request toserver APP 6440.

In one or more embodiments, providing the second request to server APP6440 can include initiating a remote procedure call (RPC) with serverAPP 6440. For example, providing the second request to server APP 6440can include utilizing a RPC framework and/or a RPC functional library.For instance, providing the second request to server APP 6440 caninclude initiating a Thrift request with server APP 6440. In one or moreembodiments, Thrift can include one or more a library (e.g., a softwarelibrary) and one or more code generation tools that can be utilized todefine data types and service interfaces in a language-neutral file andgenerate instructions (e.g., software executable by a processing system)that can be utilized in RPC clients and servers that are executable onrespective computing devices.

At 6630, address information can be received. For example, API serverAPP 6450 can receive the address information from the other server APP(e.g., server APP 6440). In one or more embodiments, the addressinformation from the other server can include one or more of an IPaddress, a port number (e.g., a TCP port number, a UDP port number,etc.), and audio proxy information, among others. In one example, one ormore of the IP address and the port number can be utilized with avirtual network console (VNC) and/or a remote network console. In asecond example, one or more of the IP address and the port number can beutilized with one or more of a remote desktop connection, an Appleremote desktop connection, and a remote X11 session or connection, amongothers. In another example, the audio proxy information can includeinformation associated with a websocket proxy.

In one or more embodiments, a first computing device and a secondcomputing device can communicate via a websocket API and/or protocol. Inone example, the first computing device can provide, via a network, afirst set of one or more TCP packets to a second computing device viathe websocket API and/or protocol. For instance, providing the first setof one or more TCP packets to the second computing device can includeproviding, via HTTP or HTTPS, the first set of one or more TCP packetsto the second computing device. In another example, the second computingdevice can provide, via the network, a second set of one or more TCPpackets to the first computing device via the websocket API and/orprotocol. For instance, providing the second set of one or more TCPpackets to the second computing device can include providing, via HTTPor HTTPS, the second set of one or more TCP packets to the firstcomputing device.

At 6640, the address information, received at 6630, can be provided tothe CCD. For example, API server APP 6450 can provide the addressinformation to the CCD. For instance, API server APP 6450 can provide aXHR object that includes the address information to the CCD. In one ormore embodiments, the CCD can utilize the address information tocommunicate with emulator proxy 6430.

Turning now to FIG. 6G, an exemplary method of operating a server APP isillustrated, according to one or more embodiments. In one or moreembodiments, the method illustrated in FIG. 6G can be utilized inoperating server APP 6440 or other server APPs that include same orsimilar one or more functionalities of server APP 6440. At 6710, thesecond request (e.g., provided at 6620 can be received. For example,server APP 6440, included in and/or executed by media server 1211, canreceive the second request from API server APP 6450.

At 6720, an emulator allocation request can be provided to an emulatorserver APP. For example, server APP 6440 can provide an emulatorallocation request to an emulation server APP 6410. At 6730, a responsefrom the emulator server APP can be received. For example, server APP6440 can receive, from emulator server APP 6410, a response to theemulator allocation request.

At 6740, it can be determined if the response from the emulator serverAPP indicates that an emulator has been allocated. For example, serverAPP 6440 can determine if the response from the emulator server APPindicates that an emulator has been allocated. If the response from theemulator server APP indicates that an emulator has not been allocated,another emulator server APP can be determined at 6750. For example,server APP 6440 can determine another emulator server APP (e.g.,different from emulator server APP 6410 such as server APP 6411). At6760, an emulator allocation request can be provided to the otheremulator server APP, and the method can proceed to 6730. For example,server APP 6440 can provide an emulator allocation request to the otheremulation server APP.

If the response from the emulator server APP indicates that an emulatorhas been allocated, address information associated with one or more ofan emulator and an emulator proxy can be determined, at 6770. In oneexample, server APP 6440 can determine the information associated withone or more of the emulator and the emulator proxy from the responsefrom the emulator server APP and/or based on the response from theemulator server APP.

In another example, server APP 6440 can receive additional informationfrom the emulator server APP and can determine the informationassociated with one or more of the emulator and the emulator proxy fromthe additional information from the emulator server APP and/or based onthe additional information from the emulator server APP. At 6780, theaddress information can be provided to the API server APP. For example,server APP 6440 can provide the address information associated with oneor more of the emulator and the emulator proxy to API server APP 6450.

Turning now to FIG. 6H, an exemplary method of operating an emulatorserver APP is illustrated, according to one or more embodiments. At6810, an emulator allocation request can be received. For example,server APP 6410 can receive an emulator allocation request from serverAPP 6440. At 6820, it can be determined if an emulator can be allocated.For example, server APP 6410 can determine if an emulator can beallocated. In one or more embodiments, determining if an emulator can beallocated can include determining one or more of an amount of memory isavailable, a thread can be allocated, a process can be allocated, a taskcan be allocated, a processing load is below a threshold, and an amountof bandwidth is below a threshold, among others. If an emulator is notallocated, a response that indicates that an emulator has not beenallocated can be provided, at 6830. For example, server APP 6410 canprovide, to server APP 6440, a response that indicates that an emulatorhas not been allocated.

If an emulator can be allocated, an emulator can be allocated, at 6840.For example, server APP 6410 can allocate an emulator. For instance,server APP 6410 can allocate an emulator such as an emulator ofemulators 6420-6422. In one or more embodiments, allocating an emulatorcan include marking an emulator, from a pool of available emulators, asno longer available to be allocated by an allocation request andproviding the marked emulator as available to a requestor.

In one or more embodiments, an emulator can emulate a data processingsystem. In one example, the emulated data processing system can includean emulated memory coupled to an emulated processor that executesinstructions from an ISA (instruction set architecture) that can bestored in the emulated memory. In one instance, the emulated processorcan execute instructions from at least one of an ARM ISA, a MIPS ISA, anx86 ISA, a PowerPC ISA, and a DSP (digital signal processing) ISA, amongothers.

In a second instance, the emulated memory can include at least one ofemulated DRAM (dynamic random access memory), SRAM (static random accessmemory), FRAM (ferroelectric random access memory), FLASH memory (e.g.,NAND FLASH memory), EEPROM (electrically erasable read only memory),EPROM (erasable programmable read only memory), PROM (programmable readonly memory), and ROM (read only memory), among others. In a thirdinstance, the emulated data processing system can include at least oneemulated bus, coupled to the emulated processor, such as at least oneemulated bus of an I²C (inter-integrated circuit) bus, an universalserial bus (USB), a serial peripheral interconnect (SPI) bus, aperipheral component interconnect (PCI) bus, a peripheral componentinterconnect express (PCIe), and an advanced high-performance bus (AHB),among others.

In another instance, one or more emulated devices and/or interfaces canbe coupled to the emulated processor, such as one or more of an emulatedwireless Ethernet interface (e.g., a WiFi interface), an Ethernetinterface, a global positioning system (GPS) receiver device, a GSM(global system for mobile communications) interface, a CDMA (codedivision multiple access) interface, a WiMAX interface, a proximitysensing device, a Bluetooth interface, a ZigBEE interface, amagnetometer, an accelerometer, a pressure transducer, a humiditysensing device, a capacitive sensing touch device, a resistive sensingtouch device, an electronic gyroscope, a gas sensing device, an imagesensing device (e.g., a digital camera), a sound sensing device (e.g., amicrophone), a sound output device (e.g., a speaker), a digital compassdevice, a temperature sensing device, a FM radio receiving device (e.g.,tunable to one or more frequencies of 87.5 MHz-108 MHz, 76 MHz-90 MHz,162.4 MHz-162.55 MHz, etc.), a FM radio transmitting device (e.g.,tunable to one or more frequencies of 87.5 MHz-108 MHz, 76 MHz-90 MHz,etc.), a light sensing device, a proximity sensing device, a radiofrequency identification (RFID) sensing device, a RFID transmittingdevice, a near field communication (NFC) device, and a range determiningdevice, among others.

In another example, the emulated data processing system can include adata processing emulator such as QEMU, SPIM, VMware, VirtualBox, orBochs, among others. In one instance, SPIM can emulate a processor thatcan execute instructions from a MIPS ISA. In a second instance, QEMU canemulate a processor that can execute instructions from an IA-32 (e.g.,x86) ISA, a MIPS ISA, a SPARC ISA, an ARM ISA, and a PowerPC ISA, amongothers. In another instance, QEMU, SPIM, VMware, VirtualBox, or Bochscan emulate one or more a memory system, a bus, a device, and aninterface, among others, coupled to an emulated processor. In one ormore embodiments, an emulator (e.g., an emulator of emulators 6420-6422)can be or include a virtual machine.

In one or more embodiments, an emulator (e.g., an emulator of emulators6420-6422) can emulate and/or simulate one or more of a physicalwireless telephone, a physical personal audio device, a physical tabletcomputing device, and a physical MP3 player, among others, and theemulator can execute an operating system and/or platform. In oneexample, the emulator can execute a Linux operating system and/orplatform. In a second example, the emulator can execute an Androidoperating system and/or platform. In a third example, the emulator canexecute an iOS operating system and/or platform. In a fourth example,the emulator can execute a BSD (Berkeley Software Distribution)operating system and/or platform. In a fifth example, the emulator canexecute a Windows CE operating system and/or platform. In sixth example,the emulator can execute a Windows Mobile operating system and/orplatform. In another example, the emulator can execute a VxWorksoperating system and/or platform.

In one or more embodiments, the emulator can execute a data generatingthread, task, and/or process that can emulate, simulate, and/or providean operating system and/or platform with data associated with one ormore functionalities of an emulated device (e.g., a physical wirelesstelephone, a physical personal audio device, a physical tablet computingdevice, a physical MP3 player, etc.). In one example, the datagenerating thread and/or process can provide the operating system and/orplatform with data that emulates and/or simulates an incoming telephonecall.

In one instance, the data generating thread and/or process can providethe operating system and/or platform with data that emulates and/orsimulates GSM data. In a second instance, the data generating threadand/or process can provide the operating system and/or platform withdata that emulates and/or simulates CDMA data. In a third instance, thedata generating thread and/or process can provide the operating systemand/or platform with data that emulates and/or simulates GPS data. Infourth instance, the data generating thread and/or process can providethe operating system and/or platform with data that emulates and/orsimulates frequency modulation (FM) data (e.g., sounds and/or text datacarried via a FM carrier wave). In another instance, the data generatingthread and/or process can provide the operating system and/or platformwith data that emulates and/or simulates amplitude modulation (AM) data(e.g., sounds and/or text data carried via a AM carrier wave).

In a second example, the data generating thread and/or process canprovide the operating system and/or platform with data that emulatesand/or simulates short messaging system (SMS) data. For instance, thedata generating thread and/or process can provide the operating systemand/or platform with data that emulates and/or simulates a SMS textmessage. In a third example, the data generating thread and/or processcan provide the operating system and/or platform with data that emulatesand/or simulates user input data. In one instance, the data thatemulates and/or simulates user input data can be generated in responseto user input data from a service representative. In another instance,the data that emulates and/or simulates user input data can be generatedin response to user input data from a customer via a CCD utilized by thecustomer.

At 6850, a response that indicates that an emulator has been allocatedcan be provided. For example, server APP 6410 can provide, to server APP6440, a response that indicates that an emulator has been allocated. At6860, input/output (I/O) of the allocated emulator can be coupled to anemulator proxy. For example, server APP 6410 can couple I/O of theallocated emulator to emulator proxy 6430. For instance, server APP 6410can couple I/O of an emulator of emulators 6420-6422 to emulator proxy6430.

In one or more embodiments, utilizing emulator proxy 6430 can prohibitdirect access of one or more clients (e.g., one or more of CCDs1111-1113) to one or more emulators (e.g., one or more of emulators6420-6422). For example, prohibiting direct access of one or moreclients to one or more emulators can include providing and/orimplementing access control. In one instance, providing and/orimplementing access control can include limiting a number of ports(e.g., TCP ports, UDP ports, etc.) of one or more emulators that one ormore clients can access. In another instance, providing and/orimplementing access control can include limiting an amount of time thatone or more clients can access one or more emulators and/or can includetiming out one or more communication couplings after an amount of timetranspires without communication activity and/or data.

In one or more embodiments, utilizing emulator proxy 6430 can bridgeaccess of one or more clients (e.g., one or more of CCDs 1111-1113)utilizing a first communication protocol to one or more emulators (e.g.,one or more of emulators 6420-6422) utilizing a second communicationprotocol. For example, the first communication protocol (e.g., awebsocket protocol) can be different from the second communicationprotocol (e.g., a transmission control protocol). For instance, bridgingaccess of one or more clients utilizing the first communication protocolto one or more emulators utilizing the second communication protocol caninclude translating and/or transforming data of the first communicationprotocol into data of the second communication protocol and/or caninclude translating and/or transforming data of the second communicationprotocol into data of the first communication protocol.

In one or more embodiments, I/O of an emulator can include video output.For example, the video output can include output that would be displayedon a screen of a device (e.g., a wireless telephone, a personal audiodevice, a tablet computing device, a MP3 player, etc.), and the videooutput can be provided to a client (e.g., a CCD of CCDs 1111-1113). Forinstance, providing the video output to the client can include providingthe video output to the client via emulator proxy 6430 and/or network1010. In an example, the I/O of an emulator can be implemented via a VNCprotocol and/or interface. In one instance, the emulator can providevideo output to the client via the VNC protocol and/or interface. Inanother instance, an operating system and/or kernel executing on theemulator can provide video output to the client via the VNC protocoland/or interface.

In one or more embodiments, I/O of an emulator can include audio output.For example, the audio output can include sounds that would be producedand/or reproduced via a device (e.g., a wireless telephone, a personalaudio device, a tablet computing device, a MP3 player, etc.), and theaudio output can be provided to a client (e.g., a CCD of CCDs1111-1113). For instance, providing the audio output to the client caninclude providing the audio output to the client via emulator proxy 6430and/or network 1010. In an example, the I/O of an emulator can beimplemented via a websocket protocol and/or interface.

In one or more embodiments, the audio output can include one or more ofpulse width modulation data, pulse code modulation data, raw audio data,WAV audio data, AIFF audio data, AAC audio data, MPEG audio data, OGGaudio data, Real Audio audio data, and WMA audio data, among others. Inone example, the emulator can provide audio output to the client via thewebsocket protocol and/or interface. In another example, an operatingsystem and/or kernel executing on the emulator can provide audio outputto the client via the websocket protocol and/or interface.

In one or more embodiments, the method illustrated in FIG. 6H can beutilized by multiple emulators. In one example, two or more differentemulators can emulate a same physical mobile device. In another example,two or more different emulators can emulate different respectivephysical mobile devices, and the two or more emulators emulatingdifferent respective physical mobile devices can perform differently inaccordance with functionalities, devices, and/or structures associatedwith the different respective physical mobile devices.

In one or more embodiments, a first emulator can emulate a firstphysical device, and a second, different, emulator can emulate a second,different, physical device. For example, a first emulated mobile device,emulated via the first emulator, that corresponds to a first physicalmobile device that can include a first physical processor, a firstphysical memory, and a first physical integrated circuit can bedifferent from a second emulated mobile device, emulated via the secondemulator, that corresponds to a second physical mobile device that caninclude a second physical processor, a second physical memory and asecond physical integrated circuit, where at least one of the firstphysical processor, the first physical memory, and the first physicalintegrated circuit is different from a corresponding one of the secondphysical processor, the second physical memory and the second physicalintegrated circuit.

In one instance, the first physical integrated circuit can include oneor more of a WiFi device (e.g., a WiFi interface), WiMAX device (e.g., aWiMAX interface), a GPS device, a GSM device (e.g., a GSM interface), aCDMA device (e.g., a CDMA interface), a satellite telephone networkinterface, a Bluetooth device (e.g., a Bluetooth interface), a ZigBEEdevice (e.g., a ZigBEE interface), a GPS device, an Ethernet device(e.g., an Ethernet interface), a proximity sensing device, amagnetometer, an accelerometer, a pressure transducer, a humiditysensing device, a capacitive sensing touch device, a resistive sensingtouch device, an electronic gyroscope, a gas sensing device, an imagesensing device (e.g., a digital camera), a sound output device, a soundsensing device (e.g., a microphone), a digital compass device, atemperature sensing device, a FM radio receiving device, a FM radiotransmitting device, a light sensing device, a RFID sensing device, aRFID transmitting device, a NFC device, and a range determining device,among others. In a second instance, the first emulator can emulate aniPhone 4 that includes an Apple A4 processor, and the second emulatorcan emulate an iPhone 4S that includes an Apple A5 processor.

In third instance, the first emulator can emulate a first wirelesstelephone that includes a CDMA wireless telephone network interface, andthe second emulator can emulate a wireless telephone that includes a GSMwireless telephone network interface. In fourth instance, the firstemulator can emulate a first wireless telephone that includes a cellularwireless telephone network interface, and the second emulator canemulate a second wireless telephone that includes a satellite wirelesstelephone network interface. In a fifth instance, the first emulator canemulate a first wireless telephone that includes a first integratedcircuit, and the second emulator can emulate a second wireless telephonethat includes a second integrated circuit that is different from thefirst integrated circuit. In a sixth instance, the first emulator canemulate a first wireless telephone that includes a Trimble GPS device,and the second emulator can emulate a wireless telephone that includes aublox GPS device. In another instance, the first emulator can emulate afirst physical device that includes an integrated circuit (e.g., anaudio integrated circuit, a graphics processing unit, a GPS integratedcircuit, etc.), and the second emulator can emulate a second physicaldevice that does not includes the integrated circuit.

Turning now to FIG. 6I, an exemplary method of operating a client thatcan interact with an emulator is illustrated, according to one or moreembodiments. At 6910, functionality can be determined. For example,functionality of a client device for providing the GUI can bedetermined. For instance, functionality of a client interface can bedetermined via a scripting functionality. In one or more embodiments,the client interface can implement a media interface (e.g., a mediainterface of media interfaces 6540-6542). For example, the clientinterface can include a web browser, and functionality of the webbrowser can be determined. For instance, functionality of the webbrowser can include one or more of a scripting functionality, a plug-infunctionality, a virtual machine functionality, and a markup languagefunctionality, among others. In one or more embodiments, determiningfunctionality can include determining a version of a functionality.

At 6920, emulation interface instructions and data can be received. Forexample, the client interface and/or a media interface can receive theemulation interface instructions and the emulation interface data from amedia server via network 1010. For example, the client interface caninclude a web browser, and the web browser can receive the emulationinterface instructions and the emulation interface data.

In one or more embodiments, the emulation interface instructions caninclude one or more of a script, executable byte code, and executablecode for a plugin, among others. In one example, the emulation interfaceinstructions can include the script that can be in accordance with ascripting language such as JavaScript, EMCAScript, Ruby, Python, or Lua,among others. In a second example, the executable byte code can be inaccordance with one or more of Ruby byte code, Python byte code, Luabyte code, Ruby byte code, and Java byte code, among others. Forinstance, the byte code can be executed by a virtual machine. In anotherexample, the executable code for a plugin can include Adobe Flashexecutable code, Java executable code, Ruby executable code, and Luaexecutable code, among others. In one or more embodiments, the emulationinterface data can include one or more of a graphic and data of a markuplanguage. For example, the markup language can include one or more ofHTML and XML, among others.

At 6930, a user interface can be configured. For example, a mediainterface (e.g., a media interface of media interfaces 6540-6542) can beconfigured based on the emulation interface instructions (e.g.,instructions associated with a scripting language such as JavaScript,EMCAScript, Ruby, Python, Lua, etc. and/or instructions associated withRuby byte code, Python byte code, Lua byte code, Java byte code, etc.)and/or the emulation interface data (e.g., HTML data, XML data, etc.).

At 6940, information can be displayed to the customer via the userinterface. For example, a media interface (e.g., a media interface ofmedia interfaces 6540-6542) can display the information to the customerbased on the emulation interface instructions and/or the emulationinterface data. At 6950, the user interface (e.g., a media interface)can couple with an emulator (e.g., an emulator of emulators 6420-6422).For example, a media interface can couple with an emulator via network1010 and/or emulator proxy 6430.

At 6960, input data can be received. In one example, a media interfacecan receive the input data from an emulator. For instance, the mediainterface can receive the input data from the emulator via network 1010and/or emulator proxy 6430. In another example, the media interface canreceive the input data from a customer (e.g., user input data). In oneor more embodiments, input from the customer can include one or more ofa selection of a graphic, a selection of an icon, a selection of a key(e.g., a key from a keypad, a key from a keyboard, etc.), visual input(e.g., one or more images from a camera coupled to a CCD), and soundinput (e.g., one or more sounds from a microphone coupled to a CCD),among others.

At 6960, a source of the input data can be determined. If the source ofthe data is determined to be from the emulator, information can bedisplayed and/or sounds can be produced for the user (e.g., customer)via the media interface and/or a sound output device of a CCD, at 6970.In one or more embodiments, the method can proceed to 6960, wherefurther information can be received. If the source of the data isdetermined to be from the user, the user input data can be provided tothe emulator, at 6980. For example, the user input data can be providedto the emulator via network 1010 and/or emulator proxy 6430. In one ormore embodiments, the method can proceed to 6960, where furtherinformation can be received.

Turning now to FIG. 6J, an exemplary method of providing multiplesimulated objects to multiple CCDs is illustrated, according to one ormore embodiments. At 6982, first information, associated with a firstnetwork address, can be received via a network. For example, the firstinformation can be received from a first CCD (e.g., CCD 1110). At 6984,second information, associated with a second network address, can bereceived via the network. For example, the second information can bereceived from a second CCD (e.g., CCD 1111). In one or more embodiments,at least one of the first information and the second information caninclude a request for a simulated object and/or a request to interactwith a simulated object.

At 6986, third information, associated with the first network address,can be provided to the network. For example, the third information canbe addressed to the first network address (e.g., associated with thefirst CCD). In one or more embodiments, the third information caninclude first data utilizable, by a first client interface associatedwith the first CCD, to display a three-dimensional simulation of a firstsimulated object and/or to change a viewing angle of the first simulatedobject.

At 6988, fourth information, associated with the second network address,can be provided to the network. For example, the fourth information canbe addressed to the second network address (e.g., associated with thesecond CCD). In one or more embodiments, the fourth information caninclude second data utilizable, by a second client interface associatedwith the second CCD, to display a three-dimensional simulation of afirst simulated object and/or to change a viewing angle of the firstsimulated object.

Turning now to FIG. 7A, a mobile device that emulates a physical deviceis illustrated, according to one or more embodiments. As shown, mobiledevice 5510 can include a display 7120, a touch screen 7130, a soundoutput device 7150 (e.g., a speaker), and one or more buttons 7140-7144.Mobile device 5510 can also include a sound input device (e.g., amicrophone), which is not shown. In one or more embodiments, MD 5510 caninclude one or more structures and/or one or more functionalitiesdescribed with reference to one or more mobile devices, one or morecomputer systems, and/or one or more computing devices described herein.

As illustrated, display 7120 can display a client interface 7520 thatcan include an interactive media interface 7530 that can include a mediainterface 7540. In one or more embodiments, client interface 7520, mediainterface 7530, and media interface 7540 can include one or morestructures and/or functionalities of client interface 3020, mediainterface 3030, and media interface 3040, respectively. As shown, mediainterface 7540 can display one or more icons/buttons 7610-7616, one ormore of icons/buttons 7240-7244, emulated display 7220, and/or emulatedtouch screen 7230, among others. In one or more embodiments, MD 5510 caninclude one or more structures and/or functionalities as those describedwith reference to a CD 7811, illustrated in FIGS. 7C and 7D.

In one or more embodiments, client interface 7520 can provideinteractivity between a user and an emulated mobile device. For example,client interface 7520 can provide interactivity between user 5010 and anemulated mobile device emulated via emulator 6422. For instance,emulator 6422 can be configured with CFG 5310 that can produce and/orimplement an emulated device (ED) 7836 (illustrated in FIGS. 7C and 7D),emulated via physical MD 5510. In one or more embodiments, CFG 5310 caninclude one or more of emulator 6422 and MDD 7838. In one example,receiving CFG 5310, as illustrated in FIG. 5H, can include receivingemulator 6422 and/or ED 7836. In another example, receiving CFG 5310, asillustrated in FIG. 5H, can include receiving MDD 7838 and/or ED 7836.

With reference again to FIG. 7A, MD 5510 can host an emulated device ina seamless fashion, according to one or more embodiments. For example,one or more of virtual display 7220, virtual touch screen 7230, andvirtual buttons 7240-7244 can be mapped to respective physical one ormore of display 7120, touch screen 7130, and buttons 7140-7144.

In one or more embodiments, user input can halt the emulated deviceand/or return control to physical MD 5510. For example, the user canselect a button, a combination of buttons, and/or an icon to halt theemulated device and/or return control to physical MD 5510. In oneinstance, the user can concurrently actuate buttons 7140 and 7144 tohalt the emulated device and/or return control to physical MD 5510. In asecond instance, the user can concurrently actuate button 7144 andselect icon 7616 to halt the emulated device and/or return control tophysical MD 5510. In another instance, the user can select icon 7616 tohalt the emulated device and/or return control to physical MD 5510.

In one or more embodiments, returning control to a physical MD caninclude returning control and/or focus to an OS and/or APP of thephysical MD. In one example, returning control to physical MD 5310 caninclude returning control and/or focus to OS 7835 (illustrated in FIGS.7C and 7D). In another example, returning control to physical MD 5310can include returning control and/or focus to APP 7832 (illustrated inFIGS. 7C and 7D).

Turning now to FIG. 7B, an exemplary illustration of a walk-through ofan emulated device is provided, according to one or more embodiments. Asshown, a beacon 7620 can be utilized to highlight and/or signal anintended action and/or a motion of the user interaction with theemulated device. For instance, beacon 7620 can be utilized within atransparent layer to highlight and/or signal an intended action and/or amotion of the user interaction with the emulated device. In one or moreembodiments, beacon 7620 can be utilized with an application-basedtutorial, set-up, and/or walk-through, described herein, that canwalk/step a user through steps to use an APP of an emulated device(e.g., ED 7836). For example, ED 7836 can emulate CD 2000.

Turning now to FIG. 7C, an exemplary computing device is illustrated,according to one or more embodiments. As shown, CD 7811 can include aprocessor 7810 coupled to a memory medium 7820. In one or moreembodiments, memory medium 7820 can store data and/or instructions thatcan be executed by processor 7810. For example, memory medium 7820 canstore one or more APPs 7830-7832, an OS 7835, mobile device data (MDD)7837, MDD 7838, client app 7821, emulator 6422, CFG 5310, SIP/VoIP proxy7222, and/or SMS proxy 7223. For instance, one or more of APPs7830-7832, OS 7835, client app 7821, emulator 6422, SIP/VoIP proxy 7222,and SMS proxy 7223 can include instructions of an ISA associated withprocessor 7810. In one or more embodiments, one or more of the processesand/or methods described here can be implemented when processor 7810executes one or more of APPs 7830-7832, OS 7835, client app 7821,emulator 6422, SIP/VoIP proxy 7222, and SMS proxy 7223. In one or moreembodiments, one or more of SIP/VoIP proxy 7222 and SMS proxy 7223 caninclude one or more structures and/or functionalities as those describedwith reference to respective one or more of SIP/VoIP proxy 23210 and SMSproxy 23220, illustrated in FIG. 23.

In one or more embodiments, a client app 7821 coupled to emulator 6422.For example, client app 7821 and emulator 6422 can communicate via oneor more processes and/or methods described herein. In one or moreembodiments, client app 7821 can be or include client interface 7520(illustrated in FIGS. 7A and 7B). For example, a user of local MD 5510(implementing and/or including one or more structures and/orfunctionalities of CD 7811) can control and/or utilize emulator as atelephone via one or more of client interface 7520, interactive mediainterface 7530, and media interface 7540. In one or more embodiments,one or more interactions with emulator 6422 can be conducted via a webbrowser interfacing with a web server of emulator 6422.

In one or more embodiments, MDD can include data and/or configurationdata associated with a MD. In one example, the MDD can include one ormore sound recordings (e.g., MP3 songs, musical pieces, voice memos,conversations, lectures, etc.), one or more contacts (e.g., contactinformation associated with people, places, companies, etc.), one ormore bookmarks (e.g., web browser book marks), one or more ebooks, oneor more social networking sites' respective information (e.g., Facebookinformation, Twitter information, MySpace information, Foursquareinformation, Last.fm information, Google+ information, etc.) associatedwith a user of the MD, one or more mobile device apps (e.g., smart phoneapps, tablet computer apps, music player apps, etc.), and/or one or moreconfigurations of the MD associated with the MDD, among others.

As illustrated, CD 7811 can include a display 7840 coupled to processor7810. In one or more embodiments, display 7840 can be utilized todisplay one or more of graphics and/or videos to a user. As shown, CD7811 can include a network interface 7880. In one example, networkinterface 7880 can interface with a wired network coupling, such as awired Ethernet, a T-1, a DSL modem, a PSTN, or a cable modem, amongothers. In another example, network interface 7880 can interface with awireless network coupling, such as a satellite telephone system, acellular telephone system, WiMax, WiFi, or wireless Ethernet, amongothers.

As shown, CD 7811 can include a speaker 7850 coupled to processor 7810.In one or more embodiments, speaker 7850 can output one or more soundsthat can be received, aurally, by a user of CD 7811. In one or moreembodiments, speaker 7850 can be coupled to processor 7810 via a digitalto analog converter (DAC). For example, the DAC can receive digitalsignals from processor 7850 and transform the digital signals to analogsignals.

As illustrated, CD 7811 can include a microphone 7860 coupled toprocessor 7810. In one or more embodiments, microphone 7860 can receiveaudio signals and can transform the audio signals into one or morevoltage signals, one or more current signal, and/or one or more digitalsignals that can be utilized by processor 7810. For example, an analogto digital converter (ADC) can be utilized to transform the one or morevoltage signals and/or the one or more current signal into the one ormore digital signals that can be utilized by processor 7810. In one ormore embodiments, the ADC can interpose processor 7810 and microphone7860 such that microphone 7860 is coupled to processor 7810 via the ADC.

As shown, CD 7811 can include a camera 7870 coupled to processor 7810.In one or more embodiments, camera 7870 can include one or more imageand/or light sensors that can transform received light signals into oneor more digital signals that can be utilized by processor 7810. In oneor more embodiments, CD 7811 can be coupled to and/or include one ormore of a keyboard and a pointing device (e.g., a mouse, a track ball, atrack pad, a stylus, etc.). In one or more embodiments, a touch screencan function as a pointing device. In one example, the touch screen candetermine a position via one or more pressure sensors. In anotherexample, the touch screen can determine a position via one or morecapacitive sensors.

In one or more embodiments, one or more elements of CD 7811 can beexternal to CD 7811. For example, as illustrated in FIG. 7D, one or moreof display 7840, speaker 7850, microphone 7860, and camera 7870 can beexternal to CD 7811. In one instance, one or more of display 7840,speaker 7850, microphone 7860, and camera 7870 can be coupled to CD 7811in a wired fashion. In another instance, one or more of display 7840,speaker 7850, microphone 7860, and camera 7870 can be coupled to CD 7811in a wireless fashion.

Turning now to FIGS. 8-10, exemplary network systems that supportsstorage of data and configurations of physical mobile devices areillustrated, according to one or more embodiments. As shown in FIG. 8,MDD 8110 associated with MD 6110 can be stored via storage 6120 that canbe included in CS 5210. In one or more embodiments, MDD can include dataand/or configuration data associated with a MD. In one example, the MDDcan include one or more sound recordings (e.g., MP3 songs, musicalpieces, voice memos, conversations, lectures, etc.), one or morecontacts (e.g., contact information associated with people, places,companies, etc.), one or more bookmarks (e.g., web browser book marks),one or more ebooks, one or more social networking sites' respectiveinformation (e.g., Facebook information, Twitter information, MySpaceinformation, Foursquare information, Last.fm information, Google+information, etc.) associated with a user of the MD, one or more mobiledevice apps (e.g., smart phone apps, tablet computer apps, music playerapps, etc.), and/or one or more configurations of the MD associated withthe MDD, among others. As illustrated, in FIG. 9, MDD 8111 associatedwith MD 6111 can be stored via storage 6121 that can be coupled to CS5210. As shown in FIG. 10, MDD 8111 associated with MD 6112 can bestored via storage 6122 that can be coupled to network 1010.

In one or more embodiments, a MD can include executable instructions(e.g., an application, a utility, an operating system, a portion of anoperating system, etc.) that, when the executable instructions areexecuted by a processor of the MD, the MD can synchronize, backup,restore, and/or initialize MDD associated with the MD. In one example,the MD can synchronize and/or backup MDD associated with the MD via awired or wireless coupling to a local system (e.g., a local computersystem, a personal computer, a laptop computer system, a local officecomputer system, etc.) and/or via network 1010 to a remote system suchas CS 5210 and/or storages 6120-6122, a distributed computer system,and/or a cloud-based system. In one example, the MD can incrementallysynchronize changes in the MDD. For instance, one or moresynchronization updates can utilize one or more portions of the MDDand/or may not require a full and/or complete duplication of the MDD.

In one or more embodiments, the MDD can include information associatedwith one or more states of the MD associated with the MD. In oneexample, the MD can receive the MDD from CS 5210 and restore the MD toone or more states, based on the MDD. In another example, the MD canreceive the MDD from CS 5210 and can perform a “fresh” install, even ifthe MDD indicates a particular state or if the MD is in a particularstate. In one or more embodiments, the MD can receive user input thatindicates one or more selected items to restore which can be in additionto what is present and/or to overwrite existing properties/data.

Turning now to FIGS. 11-13, exemplary network systems that supportrecovery and/or restoration of data and configurations of physicalmobile devices are illustrated, according to one or more embodiments. Asshown in FIG. 11, MDD 8110 can be restored to MD 6110. As illustrated inFIG. 12, MDD 8111 can be restored to MD 6111. As shown in FIG. 13, MDD8112 can be restored to MD 6112.

In one or more embodiments, recovery and/or restoration of MDDassociated with a first MD or recovery and/or restoration of one or moreportions of the MDD associated with the first MD can be utilized withthe first MD or can be utilized with a second MD, different from thefirst MD. In one example, the first MD can be physically different fromthe second MD. For instance, the first MD can include a first processor,a first memory, and a first integrated circuit; the second MD a secondprocessor, a second memory, and a second integrated circuit; and atleast one of the first processor, the first memory, and the firstintegrated circuit can be different from a respective one of the secondprocessor, the second memory, and the second integrated circuit.

In another example, the first MD can execute an operating system and/orplatform different from the second MD. For instance, the first MD canexecute a first operating system and/or a first platform, and the secondMD can execute a second operating system and/or a second platform, whereat least one of the first operating system and the first platform can bedifferent from a respective one of the second operating system and thesecond platform. In one or more embodiments, this can allow recoveryand/or restoration of MDD onto the second MD that did not perform backupand/or synchronization methods and/or processes.

In one or more embodiments, one or more portions of the MDD may not beapplicable to the second MD. For example, the first MD can execute anAndroid operating system and/or platform, the second MD can executeWindows Mobile operating system and/or platform, and one or moreapplications (e.g., smart phone apps) may not be applicable to thesecond MD.

In one or more embodiments, one or more portions of the MDD(synchronized and/or backed up via the first MD) can be transformed,altered, converted, translated, adapted, adjusted, changed, modified,and/or adapted, among others, such that the one or more portions of theMDD can be utilized by the second MD. For example, a contact list can beincluded in the MDD, the contact list can be stored and/or indexed in aformat that is associated with an Android operating system and/orplatform, and the contact list can be transformed, altered, converted,translated, adapted, adjusted, changed, modified, and/or adapted, amongothers, such that the Windows Mobile operating system and/or platform ofthe second MD can utilize information from the contact list.

Turning now to FIG. 14, an exemplary system that supports installationof data and configurations of one or more physical mobile devices to oneor more respective emulators is illustrated, according to one or moreembodiments. In one or more embodiments, one or more emulators canemulate one or more physical mobile devices. In one example, emulator6422 can emulate MD 6110, emulator 6423 can emulate MD 6111, and/oremulator 6424 can emulate MD 6112. As shown, MDD 8110 can be copiedand/or transferred to emulator 6422. In another example, emulator 6422can emulate MD 6110, emulator 6423 can emulate MD 6111, and/or emulator6424 can emulate MD 6112. As shown, MDD 8110 or one or more portions ofMD 8110 can be copied and/or transferred to emulator 6422; MDD 8111 orone or more portions of MD 8111 can be copied and/or transferred toemulator 6423; and MDD 8112 or one or more portions of MD 8112 can becopied and/or transferred to emulator 6424.

In one or more embodiments, one or more portions of MDD can be copiedand/or transferred to an emulator when a method and/or process of and/orassociated with the emulator requests the one or more portions of theMDD. In one example, one or more portions of MDD 8110 can be copiedand/or transferred to emulator 6422 when a method and/or process ofand/or associated with emulator 6422 requests the one or more portionsof MDD 8110. In a second example, one or more portions of MDD 8111 canbe copied and/or transferred to emulator 6423 when a method and/orprocess of and/or associated with emulator 6423 requests the one or moreportions of MDD 8111. In another example, one or more portions of MDD8112 can be copied and/or transferred to emulator 6424 when a methodand/or process of and/or associated with emulator 6424 requests the oneor more portions of MDD 8112.

In one or more embodiments, the MDD or one or more portions of MDD canbe transformed, altered, converted, translated, adapted, adjusted,changed, modified, and/or adapted, among others, and transferred to anemulator when a method and/or process of and/or associated with theemulator requests the MDD or the one or more portions of the MDD. In oneexample, MDD 8110 or one or more portions of MDD 8110 can betransformed, altered, converted, translated, adapted, adjusted, changed,modified, and/or adapted, among others, and transferred to emulator 6422when a method and/or process of and/or associated with emulator 6422requests the one or more portions of MDD 8110. In a second example, MDD8111 or one or more portions of MDD 8111 can be transformed, altered,converted, translated, adapted, adjusted, changed, modified, and/oradapted, among others, and transferred to emulator 6423 when a methodand/or process of and/or associated with emulator 6423 requests the oneor more portions of MDD 8111. In another example, MDD 8112 or one ormore portions of MDD 8112 can be transformed, altered, converted,translated, adapted, adjusted, changed, modified, and/or adapted, amongothers, and transferred to emulator 6424 when a method and/or process ofand/or associated with emulator 6424 requests the one or more portionsof MDD 8112. In one or more embodiments, transferring data to anemulator (e.g., an emulator of emulators 6422-6423) can includeproviding availability of and/or access to the data by the emulator.

In one or more embodiments, an emulator can include executableinstructions (e.g., an application, a utility, an operating system, aportion of an operating system, etc.), that when the executableinstructions are executed by an emulated processor of the emulator, theemulator can synchronize, backup, restore, and/or initialize MDDassociated with an associated MD. In one example, the emulator caninitiate synchronization of one or more settings, one or moreconfigurations, and/or information from the MDD. In a second example,the emulator can initiate synchronization of one or more settings, oneor more configurations, and/or information from the MDD, where the MDDis associated with a MD that includes and/or executes a first operatingand/or a first platform than a second, different, operating systemand/or a second, different, platform. For instance, one or more portionsof the MDD can be transformed, altered, converted, translated, adapted,adjusted, changed, modified, and/or adapted, among others, andtransferred to the emulator when a method and/or process of and/orassociated with the emulator requests the one or more portions of theMDD associated with the MD. In one or more embodiments, one or moremodifications to the MDD and/or a base image of the emulator can bestored. For example, the one or more modifications can be storedtemporarily and erased and/or discarded after the emulator is terminatedand/or concludes operations.

In one or more embodiments, a determination of what informationassociated with the MDD to restore and/or to initialize the emulator canbe made. In one example, the determination can include a fullrestoration of the MDD to the emulator. In another example, thedetermination can include a restoration of one or more portions of theMDD to the emulator. In one or more embodiments, the determination canbe based on user input and/or one or more user preferences and/orconfigurations.

In one or more embodiments, the determination can be based on one ormore attributes associated with the emulator and/or one or moreattributes associated with the MD. In one example, the determination canbe based on one or more similarities between or among the one or moreattributes associated with the emulator and the one or more attributesassociated with the MD. In another example, the determination can bebased on one or more differences between or among the one or moreattributes associated with the emulator and the one or more attributesassociated with the MD.

In one or more embodiments, the one or attributes associated with theemulator can include one or more of an operating system, a platform, anemulated processor, an emulated memory, an emulated integrated circuit,an emulated GPU, an emulated WiFi device (e.g., an emulated WiFiinterface), an emulated WiMAX device (e.g., an emulated WiMAXinterface), an emulated GPS device, an emulated GSM device (e.g., anemulated GSM interface), an emulated CDMA device (e.g., an emulated CDMAinterface), an emulated satellite telephone network interface, anemulated Bluetooth device (e.g., an emulated Bluetooth interface), anemulated ZigBEE device (e.g., an emulated ZigBEE interface), an emulatedGPS device, an emulated Ethernet device (e.g., an emulated Ethernetinterface), an emulated proximity sensing device, an emulatedmagnetometer, an emulated accelerometer, an emulated pressuretransducer, an emulated humidity sensing device, an emulated capacitivesensing touch device, an emulated resistive sensing touch device, anemulated electronic gyroscope, an emulated gas sensing device, anemulated image sensing device (e.g., an emulated digital camera), anemulated sound output device, an emulated sound sensing device (e.g., anemulated microphone), an emulated digital compass device, an emulatedtemperature sensing device, an emulated FM radio receiving device, anemulated FM radio transmitting device, an emulated light sensing device,an emulated RFID sensing device, an emulated RFID transmitting device,an emulated NFC device, and an emulated range determining device, amongothers.

In one or more embodiments, the one or attributes associated with the MDcan include one or more of an operating system, a platform, a processor,a memory, an integrated circuit, a GPU, a WiFi device (e.g., a WiFiinterface), WiMAX device (e.g., a WiMAX interface), a GPS device, a GSMdevice (e.g., a GSM interface), a CDMA device (e.g., a CDMA interface),a satellite telephone network interface, a Bluetooth device (e.g., aBluetooth interface), a ZigBEE device (e.g., a ZigBEE interface), a GPSdevice, an Ethernet device (e.g., an Ethernet interface), a proximitysensing device, a magnetometer, an accelerometer, a pressure transducer,a humidity sensing device, a capacitive sensing touch device, aresistive sensing touch device, an electronic gyroscope, a gas sensingdevice, an image sensing device (e.g., a digital camera), a sound outputdevice, a sound sensing device (e.g., a microphone), a digital compassdevice, a temperature sensing device, a FM radio receiving device, a FMradio transmitting device, a light sensing device, a RFID sensingdevice, a RFID transmitting device, a NFC device, and a rangedetermining device, among others.

Turning now to FIGS. 15-17, exemplary local area network systems thatsupport storage of data and configurations of physical mobile devicesare illustrated, according to one or more embodiments. As shown in FIG.15, MDD 8110 associated with MD 6110 can be stored via storage 15510that can be included in a local CS 15011. As illustrated, MD 6110 andlocal CS 15011 can be coupled to a local area network (LAN) 15010. Inone or more embodiments, local CS 15011 can include one or more of acomputer system, a server computer system, a laptop computer system, anotebook computing device, a portable computer, a network appliance, atelevision device, a DVD (digital video disc player) device, a Blu-Raydisc player device, a DVR (digital video recorder) device, or otherwireless or wired device that includes a processor that executesinstructions from a memory medium.

In one or more embodiments, LAN 15010 can include a wired network. Inone example, LAN 15010 can include a wired network based on wiredEthernet. In another example, LAN 15010 can include a wired networkbased on wired Ethernet over one or more power lines. For instance, LAN15010 can include a wired network based on one or more of IEEE 1901,IEEE 1675, HomePNA, and HomePlug, among others. In one or moreembodiments, LAN 15010 can include a wireless network. In one example,LAN 15010 can include a wireless network based on wireless Ethernet(e.g., based on IEEE 802.11). In a second example, LAN 15010 can includea wireless network based on Bluetooth (e.g., based on IEEE 802.15). In athird example, LAN 15010 can include a wireless network based onwireless USB. In another example, LAN 15010 can include a wirelessnetwork based on one or more of IEEE 802.15.4 and ZigBEE, among others.

As shown in FIG. 16, MDD 8111 associated with MD 6111 can be stored viastorage 15511 that can be coupled to local CS 15011. As illustrated FIG.17, MDD 8112 associated with MD 6112 can be stored via storage 15512that can be coupled to LAN 15010.

Turning now to FIGS. 18-20, exemplary local network systems that supportrecovery and/or restoration of data and configurations of physicalmobile devices are illustrated, according to one or more embodiments. Asshown in FIG. 18, MDD 8110 can be restored to MD 6110. As illustrated inFIG. 19, MDD 8111 can be restored to MD 6111. As shown in FIG. 20, MDD8112 can be restored to MD 6112.

Turning now to FIG. 21, an exemplary system that supports storage ofdata and configurations of physical mobile devices is illustrated,according to one or more embodiments. In one or more embodiments, MDDcan be transferred, via a network, from a first computer system to asecond computer system. As shown, local CS 15011 can be coupled tonetwork 1010. As illustrated, MDD 8110 can be transferred, via network1010, from CS 5210 to local CS 15011. As shown, MDD 8111 can betransferred, via network 1010, from CS 5210 to local CS 15011.

Turning now to FIG. 22, a network system that supports network storageof data and configurations of physical mobile devices is illustrated,according to one or more embodiments. As shown, LAN 15010 can be coupledto network 1010. In one or more embodiments, MDD can be transferred, viaa first network, from a first computer system to storage coupled to asecond network. As illustrated, MDD 8112 can be transferred, via network1010 and LAN 15010, from CS 5210 to storage 15512.

Turning now to FIG. 23, an exemplary local network system that supportsinstallation of data and configurations and utilization of an emulatoris illustrated, according to one or more embodiments. As illustrated, asession initiation protocol (SIP) gateway 23110 can be coupled tonetwork 1010. In one or more embodiments, SIP can be utilized incontrolling one or more communications sessions. For example, SIP can beutilized in controlling voice and/or video calls via a network protocol(e.g., an Internet protocol). For instance, SIP can be utilized increating, modifying two or more party communication sessions. In one ormore embodiments, the communications sessions can include one or moremedia streams.

As shown, a SMS gateway 23120 can be coupled to network 1010. In one ormore embodiments, SMS gateway 23120 can include a telecommunicationsdevice and/or facility for sending and/or receiving SMS transmissions toand/or from a telecommunications network. As illustrated, local CS 15011can include a SIP/VoIP proxy 23210 coupled to emulator 6422. In one ormore embodiments, SIP/VoIP proxy 23210 and emulator 6422 can communicatevia one or more processes and/or methods described herein. In one ormore embodiments, VoIP and/or IP encapsulated SMS and/or multimediamessaging service (MMS) termination can be implemented and/or providedwithin emulator 6422. As shown, local CS 15011 can include a SMS proxy23220 coupled to emulator 6422. In one or more embodiments, SIP/VoIPproxy 23210 and emulator 6422 can communicate via one or more processesand/or methods described herein.

In one or more embodiments, SIP gateway 23110 and SIP/VoIP proxy 23210can communicate via network 1010. For example, SIP gateway 23110 canroute telephone calls and/or video calls to and/or from SIP/VoIP proxy23210. In one instance, SIP/VoIP proxy 23210 can receive can emulate oneor more GSM and/or CDMA signals that can carry the telephone callsand/or video calls and can provide the signals that can carry thetelephone calls and/or video calls to emulator 6422. In anotherinstance, SIP/VoIP proxy 23210 can receive one or more GSM and/or CDMAemulated signals that can carry the telephone calls and/or video callsfrom emulator 6422 and can provide the telephone calls and/or videocalls to SIP gateway 23110.

As illustrated, local CS 15011 can include a client app 23230 coupled toemulator 6422. For example, client app 23230 and emulator 6422 cancommunicate via one or more processes and/or methods described herein.In one or more embodiments, local CS 15011 can be or include CCD 1111,and client app 23230 can be or include client interface 63021. Forexample, a user of local CS 15011 can control and/or utilize emulator asa telephone via one or more of client interface 63021, interactive mediainterface, and media interface 6541. In one or more embodiments, one ormore interactions with emulator 6422 can be conducted via a web browserinterfacing with a web server of emulator 6422.

In one or more embodiments, if an incoming call or an incoming messageoccurs when the web browser that would interface with the web server ofemulator 6422 is not executing or is not directed to the web server ofemulator 6422, an alert can be provided to the user of local CS 15011.In one example, the alert can include a display notification that canopen a window displayed via a display associated with local CS 15011. Inanother example, the alert can include one or more sounds. In oneinstance, the one or more sounds can include one or more sounds of atelephone ringing. In another instance, the one or more sounds caninclude one or more sounds of a message arriving.

In one or more embodiments, when emulator 6422 is not running or notexecuting, a telephone system associated with emulator 6422 and/or aphysical MD associated with emulator 6422 can function as if thephysical MD is turned off, is not functioning, and/or is not incommunication with a Node B, a base transceiver station, or a satellite.For example, a VoIP, a SMS, and/or a MMS termination point for emulator6422 can be terminated.

In one or more embodiments, local CS 15011 can include or be coupled toone or more of a camera, a display, a microphone, and a speaker. In oneexample, the microphone and the speaker associated with local CS 15011can be utilized in one or more telephonic communications. In anotherexample, the camera and the display associated with local CS 15011 canbe utilized in one or more video communications. In one or moreembodiments, local CS 15011 can include one or more structures and/orfunctionalities described with reference to CD 2000, CD 7811, and/or MD5510.

Turning now to FIG. 24, an exemplary system that supports installationof data and configurations and utilization of multiple emulators isillustrated, according to one or more embodiments. As illustrated, a SIPgateway 24110 can be coupled to network 1010. In one or moreembodiments, SIP gateway 24110 can include one or more same or similarstructures and/or functionalities as described with reference to SIPgateway 23110. As shown, a SMS gateway 24120 can be coupled to network1010. In one or more embodiments SMS gateway 24120 can include one ormore same or similar structures and/or functionalities as described withreference to SMS gateway 23120.

As illustrated, CS 5210 can include a SIP/VoIP proxy 24210 coupled toemulators 6422-6424. In one or more embodiments, SIP/VoIP proxy 24210and emulators 6422-6424 can communicate via one or more processes and/ormethods described herein. As shown, CS 5210 can include a SMS proxy24220 coupled to emulators 6422-6424. In one or more embodiments, SMSproxy 24220 and emulators 6422-6424 can communicate via one or moreprocesses and/or methods described herein. In one or more embodiments,VoIP and/or IP encapsulated SMS and/or MMS termination can beimplemented and/or provided within one or more emulators 6422-6424.

In one or more embodiments, SIP gateway 24110 and SIP/VoIP proxy 24210can communicate via network 1010. For example, SIP gateway 24110 canroute telephone calls and/or video calls to and/or from SIP/VoIP proxy24210. In one instance, SIP/VoIP proxy 24210 can receive can emulate oneor more signals (e.g., GSM signals, CDMA signals, etc.) that can carrythe telephone calls and/or video calls and can provide signals that cancarry the telephone calls and/or video calls to one or more of emulators6422-6424. In another instance, SIP/VoIP proxy 24210 can receive one ormore emulated signals (e.g., emulated GSM signals, emulated CDMAsignals, etc.) that can carry the telephone calls and/or video callsfrom one or more emulators 6422-6424 and can provide the telephone callsand/or video calls to SIP gateway 24110.

In one or more embodiments, emulators 6422-6424 can be operated and/orcontrolled by respective CCDs 1111-1113. For example, emulators6422-6424 can be operated and/or controlled by respective clientinterfaces 63021-63023. For instance, each of client interfaces63021-63023 can include a web browser that operates and/or controls arespective emulator.

In one or more embodiments, each emulator of emulators 6422-6424 canprovide and/or implement authentication, authorization, and/or accesscontrol to determine that a user can interact with, utilize, and/oroperate the emulator. For example, an emulator of emulators 6422-6424can receive identification information associated with a user and/or auser account and/or can receive a password associated with the userand/or the user account to determine that the user can interact with,utilize, and/or operate the emulator. In one instance, the emulator canauthenticate and/or authorize the identification information and/or thepassword with a database. In a second instance, the emulator canauthenticate and/or authorize the identification information and/or thepassword with at least one of a home location register (HLR) and avisiting location register (VLR), among others. In another instance, theemulator can authenticate and/or authorize the identificationinformation and/or the password with an authentication, authorization,and accounting (AAA) server and/or service.

In one or more embodiments, if an incoming call or an incoming messageoccurs when a web browser that would interface with a web server of anemulator of emulators 6422-6424 is not executing or is not directed tothe web server of the emulator, an alert can be provided to a user via aCCD (e.g., a CCD of CCDs 1111-1113) utilized by the user. In oneexample, the alert can include a display notification that can open awindow displayed via a display associated with the CCD. In anotherexample, the alert can include one or more sounds. In one instance, theone or more sounds can include one or more sounds of a telephoneringing. In another instance, the one or more sounds can include one ormore sounds of a message arriving.

In one or more embodiments, if the emulator is not running or notexecuting, a telephone system associated with the emulator and/or aphysical MD associated with the emulator can function as if the physicalMD is turned off, is not functioning, and/or is not in communicationwith a Node B, a base transceiver station, or a satellite. For example,a VoIP, a SMS, and/or a MMS termination point for the emulator can beterminated. In one or more embodiments, an alternate notificationprocess, method, and/or path can be utilized if the emulator is notrunning or not executing. In one example, a push notification can beprovided to the CDD of the user. In another example, a text message(e.g., a SMS message, an email message, etc.) indicating that anincoming telephone call, voice message, and/or other message (e.g., atext message) can be provided to another device associated with theuser. For instance, a SMS message can be provided to the other device(e.g., a wireless telephone, a pager, etc.) associated with the userand/or the identification information associated with the user.

In one or more embodiments, providing the text message (e.g., a SMSmessage, an email message, etc.) that indicates an incoming telephonecall, voice message, and/or other message (e.g., a text message) can bebased on a profile and/or a configuration associated with the user. Forexample, the profile and/or a configuration associated with the user caninclude a policy that can direct providing the text message (e.g., a SMSmessage, an email message, etc.) that indicates an incoming telephonecall, voice message, and/or other message (e.g., a text message) to theother device associated with the user and/or the identificationinformation associated with the user.

Turning now to FIG. 25, an exemplary computing system is illustrated,according to one or more embodiments. As shown, CS 5210 can include aprocessor 25010 coupled to a memory medium 25020. In one or moreembodiments, memory medium 25020 can store data and/or instructions thatcan be executed by processor 25010. For example, memory medium 25020 canstore one or more APPs 25030-25032, an OS 25035, MDDs 8110-8112,emulators 6422-6424, SIP/VoIP proxy 24210, and/or SMS proxy 24220. Forinstance, one or more of APPs 25030-25032, OS 25035, emulators6422-6424, SIP/VoIP proxy 24210, and SMS proxy 24220 can includeinstructions of an ISA associated with processor 25010. In one or moreembodiments, one or more of the processes and/or methods described herecan be implemented when processor 25010 executes one or more of APPs25030-25032, OS 25035, emulators 6422-6424, SIP/VoIP proxy 24210, andSMS proxy 24220.

As illustrated, CS 5210 can include a network interface 25040. In oneexample, network interface 2040 can interface with a wired networkcoupling, such as a wired Ethernet, a T-1, a T-3, an OC-12, a DSL modem,a PSTN, or a cable modem, among others. In another example, networkinterface 25040 can interface with a wireless network coupling, such asa satellite telephone system, a cellular telephone system, WiMax, orwireless Ethernet, among others.

Turning now to FIG. 26, an exemplary method of a computer systemreceiving and storing mobile device data is illustrated, according toone or more embodiments. At 26010, a computer system can receive one ormore portions of MDD associated with a MD. In one example, CS 5210 canreceive, via network 1010, the one or more portions of MDD associatedwith the MD. In a second example, local CS 15011 can receive, via LAN15010, the one or more portions of MDD associated with the MD. Inanother example, local CS can receive, via LAN 15010, the one or moreportions of MDD associated with the MD.

In one or more embodiments, the MDD can be associated with one of MDs6110-6112. In one example, the one or more portions of MDD associatedwith the MD can be or include an incremental backup and/orsynchronization. In another example, the one or more portions of MDDassociated with the MD can be or include all portions of the MDD. Forinstance, all portions of the MDD can be or include a “full” backup ofthe MD.

At 26020, the computer system can store the one or more portions of theMDD. In one example, the one or more portions of the MDD can be storedin non-volatile storage. In another example, the one or more portions ofthe MDD can be stored in a random access memory that can provide anemulator access to the one or more portions of the MDD in a fashion thatcan be faster than access to the one or more portions of the MDD vianon-volatile storage.

Turning now to FIG. 27, an exemplary method of a mobile device receivingand storing mobile device data is illustrated, according to one or moreembodiments. In one or more embodiments, a MD can receive can receiveone or more portions of MDD associated with the MD, at 27010. In oneexample, the MD can receive, via network 1010, the one or more portionsof MDD associated with the MD. In a second example, the MD can receive,via LAN 15010, the one or more portions of MDD associated with the MD.

In one or more embodiments, the one or more portions of MDD associatedwith the MD can be or include one or more incremental synchronizationsand/or backups. In one or more embodiments, the one or more portions ofMDD associated with the MD can be or include one or more changes of theMDD, after the MDD has been utilized by an emulator. In one example, auser can utilize the MDD via the MD, utilize the MDD via an emulatorassociated with the MD, and receive the one or more changes of the MDD,after the MDD has been utilized by an emulator.

In another example, a user can utilize the MDD via the MD, an emulatorassociated with the MD can utilize the MDD via the user and/or anotheruser (e.g., a sales representative, a service representing, arepresentative of a retail establishment, a representative of a serviceprovider, an artificial intelligence system, a neural network system,etc.), and receive the one or more changes of the MDD, after the MDD hasbeen utilized by the emulator via the user and/or the other user. Forinstance, the other user (e.g., a service representative) can assist theuser to configure his or her MD via providing the MDD to an emulator andcan change one or more portions of the MDD (e.g., one or moreconfigurations of the MD associated with the MDD), and the one or moreportions of the MDD can be received by the MD after the other userassists the user to configure his or her MD via the emulator.

In one or more embodiments, the MD can store the one or more portions ofthe MDD, at 27020. In one example, the MD can store the one or moreportions of MDD that include the one or more incrementalsynchronizations and/or backups. In a second example, the MD can storethe one or more portions of MDD that include the one or more changes ofthe MDD, after the MDD has been utilized by an emulator. In anotherexample, the MD can store the one or more portions of MDD that includethe one or more changes of the MDD after the MDD has been utilized by anemulator that was utilized by another user (e.g., a salesrepresentative, a service representing, a representative of a retailestablishment, a representative of a service provider, etc.) or anassistance system (e.g., an artificial intelligence system, a neuralnetwork system, etc.).

In one or more embodiments, the one or more portions of MDD can beassociated with a first MD, and a second MD, different from the firstMD, can receive the one or more portions of MDD associated with thefirst MD, at 27010. In one example, the MDD can be a base or a templatefor multiple MDs. For instance, MDD that can be a base or a template canbe a base or a template for multiple MDs of a sales group of a company.In a second example, the second MD can be a replacement for the firstMD. In another example, the second MD can augment and/or be an additionto the first MD. In one instance, the first MD can be or include amobile wireless telephone, and the second MD can be or include a tabletcomputing device. In a second instance, the first MD can be or include afirst mobile wireless telephone associated with a first MIN, and thesecond MD can be or include a second wireless telephone associated witha second MIN, different from the first MIN. In another instance, thefirst MD can be or include a first mobile wireless telephone, and thesecond MD can be or include an emulation of the first mobile wirelesstelephone.

In one or more embodiments, the second MD can store the one or moreportions of the MDD, at 27020. For example, the second MD can store theone or more portions of MDD associated with the first MD.

Turning now to FIG. 28, an exemplary method of transformingtelecommunications signals is illustrated, according to one or moreembodiments. At 28010, a first telecommunications signal can bereceived. In one example, the first telecommunications signal can bereceived from SIP gateway 24110. In a second example, the firsttelecommunications signal can be received from SMS gateway 24120.

In a third example, the first telecommunications signal can include aSIP telecommunications signal. For instance, SIP/VoIP proxy 24210 canreceive the SIP telecommunications signal. In a fourth example, thefirst telecommunication signal can include a VoIP telecommunicationssignal. For instance, SIP/VoIP proxy 24210 can receive the VoIPtelecommunications signal. In another example, the firsttelecommunication signal can include a SMS or MMS telecommunicationssignal. For instance, SMS proxy 24220 can receive the SMS or MMStelecommunications signal.

At 28020, the first telecommunication signal can be transformed into asecond telecommunications signal. In one example, the firsttelecommunications signal can be transformed into a CDMAtelecommunications signal. In one instance, SIP/VoIP proxy 24210 cantransform the first telecommunications signal into the CDMAtelecommunications signal. In another instance, SMS proxy 24220 cantransform the first telecommunications signal into the CDMAtelecommunications signal. In another example, the firsttelecommunications signal can be transformed into a GSMtelecommunications signal. In one instance, SIP/VoIP proxy 24210 cantransform the first telecommunications signal into the GSMtelecommunications signal. In another instance, SMS proxy 24220 cantransform the first telecommunications signal into the GSMtelecommunications signal.

At 28030, the second communications signal can be provided to anemulator. In one example, SIP/VoIP proxy 24210 can provide the secondtelecommunications to the emulator (e.g., an emulator of emulators6422-6424). In another example, SMS proxy 24220 can provide the secondtelecommunications to the emulator (e.g., an emulator of emulators6422-6424).

In one or more embodiments, the method illustrated in FIG. 28 can berepeated to transform additional telecommunications signals and providethe transformed telecommunications signals to one or more emulators. Inone or more embodiments, the second telecommunications signals can berouted to different emulators based on different network identificationsassociated with the first telecommunications signals. For example, thedifferent network identifications associated with the firsttelecommunications signals can include different IP (Internet protocol)addresses (e.g., different IP version 4 addresses, different IP version6 addresses, etc.), different MAC (media access control) addresses,different electronic serial numbers (ESNs), different mobile informationnumbers (MINs), and different mobile directory numbers (MDNs), amongothers.

Turning now to FIG. 29, an exemplary method of transformingtelecommunications signals is illustrated, according to one or moreembodiments. At 29010, a first telecommunication signal can be received.In one or more embodiments, the telecommunication signal can be receivedfrom an emulator (e.g., an emulator of emulators 6422-6424. In oneexample, the first telecommunications signal can include a CDMAtelecommunications signal. In one instance, SIP/VoIP proxy 24210 canreceive the CDMA telecommunications signal. In another instance,SIP/VoIP proxy 24210 can receive the CDMA telecommunications signal. Inanother example, the first telecommunication signal can include a GSMtelecommunications signal. In one instance, SIP/VoIP proxy 24210 canreceive the GSM telecommunications signal. In another instance, SMSproxy 24220 can receive the GSM telecommunications signal.

At 29020, the first telecommunications signal can be transformed into asecond telecommunications signal. In one example, the firsttelecommunications signal can be transformed into a SIPtelecommunications signal. For instance, SIP/VoIP proxy 24210 cantransform the first telecommunications signal into the SIPtelecommunications signal. In a second example, the firsttelecommunications signal can be transformed into a VoIPtelecommunications signal. For instance, SIP/VoIP proxy 24210 cantransform the first telecommunications signal into the VoIPtelecommunications signal. In a third example, the firsttelecommunications signal can be transformed into a SMStelecommunications signal. For instance, SMS proxy 24220 can transformthe first telecommunications signal into the SMS telecommunicationssignal. In another example, the first telecommunications signal can betransformed into a MMS telecommunications signal. For instance, SMSproxy 24220 can transform the first telecommunications signal into theMMS telecommunications signal.

At 29030, the second telecommunications signal can be provided to atelecommunications gateway. In one example, SIP/VoIP proxy 24210 canprovide the second telecommunications signal to SIP gateway 24110. Inanother example, SMS proxy 24220 can provide the secondtelecommunications signal to SMS gateway 24120.

In one or more embodiments, the method illustrated in FIG. 29 can berepeated to transform additional telecommunications signals and providethe transformed telecommunications signals to one or moretelecommunications gateways. In one or more embodiments, the secondtelecommunications signals can be routed to different telecommunicationsgateways and/or endpoints based on different network identificationsassociated with the first telecommunications signals. For example, thedifferent network identifications associated with the firsttelecommunications signals can include different IP addresses (e.g.,different IP version 4 addresses, different IP version 6 addresses,etc.), different MAC addresses, different ESNs, different MINs, anddifferent MDNs, among others.

In one or more embodiments, the methods illustrated in FIGS. 28 and 29can be utilized with local CS 15011, as well as CS 5210. For example,SIP/VoIP proxy 23210 of local CS 15011 can be utilized in place ofSIP/VoIP proxy 24210 of CS 5210, and SMS proxy 23220 of local CS 15011can be utilized in place of SIP/VoIP proxy 24220 of CS 5210.

Turning now to FIG. 30, an exemplary method of utilizing an emulator isillustrated, according to one or more embodiments. At 30010, an emulatorcan receive an invite from a telecommunications network. In one or moreembodiments, the invite can indicate that a telephone is calling theemulator.

In one or more embodiments, receiving the invite can include receivingthe signal that indicates the invite. For example, receiving, via SIP,the signal that indicates the invite can include receiving the invitevia one or more of a SIP gateway and a SIP proxy. In one instance,emulator 6422 can receive the signal that indicates the invite via SIPgateway 23110 and via SIP/VoIP proxy 23210, illustrated in FIG. 23. Inanother instance, emulator 6423 can receive the signal that indicatesthe invite via SIP gateway 24110 and via SIP/VoIP proxy 24210,illustrated in FIG. 24.

At 30020, the emulator can provide a signal to the telecommunicationsnetwork that indicates it is trying to summon a user (e.g., a calledparty). At 30030, the emulator can provide an indication of an incomingtelephone call to the user. In one example, emulator 6422 can providethe indication of the incoming telephone call to the user via client app23230. In another example, emulator 6423 can provide the indication ofthe incoming telephone call to the user via client interface 63022. Inone or more embodiments, client interface 63022 can be or include a webbrowser.

At 30040, the emulator can provide, to the telecommunications network, asignal that indicates that it is providing the indication of theincoming telephone call to the user. For example, the signal thatindicates that the emulator is providing the indication of the incomingtelephone call to the user can be provided to the telecommunicationsnetwork via SIP. In one instance, emulator 6422 can provide the signalthat indicates that emulator 6422 is providing the indication of theincoming telephone call to the user can be provided to thetelecommunications network via SIP gateway 23110 and via SIP/VoIP proxy23210, illustrated in FIG. 23. In another instance, emulator 6423 canprovide the signal that indicates that emulator 6423 is providing theindication of the incoming telephone call to the user can be provided tothe telecommunications network via SIP gateway 24410 and via SIP/VoIPproxy 24210, illustrated in FIG. 24.

At 30050, the emulator can receive user input that indicates that thetelephone call is to be answered. In one example, emulator 6422 canreceive the user input that indicates that the telephone call is to beanswered via client app 23230, illustrated in FIG. 23. In anotherexample, emulator 6423 can receive the user input that indicates thatthe telephone call is to be answered via client interface 63022,illustrated in FIG. 6E.

At 30060, the emulator can provide, to the telecommunications network, asignal that indicates the user has answered the call. For example, thesignal that indicates the user has answered the call can be provided tothe telecommunications network via SIP. In one instance, emulator 6422can provide the signal that indicates the user has answered the call canbe provided to the telecommunications network via SIP gateway 23110 andvia SIP/VoIP proxy 23210. In another instance, emulator 6423 can providethe signal that indicates the user has answered the call can be providedto the telecommunications network via SIP gateway 24410 and via SIP/VoIPproxy 24210.

At 30070, the emulator can receive an acknowledgement from thetelecommunications network. For example, a signal that indicates theacknowledgement can be received from the telecommunications network viaSIP. In one instance, emulator 6422 can receive the signal thatindicates the acknowledgement from the telecommunications network viaSIP gateway 24110 and via SIP/VoIP proxy 24210. In another instance,emulator 6423 can receive the signal that indicates the acknowledgementfrom the telecommunications network via SIP gateway 24410 and viaSIP/VoIP proxy 24210.

At 30080, the emulator can exchange data (e.g., RTP (real-time protocol)data) with the telecommunications network. In one example, emulator 6422can exchange the data with the telecommunications network via SIPgateway 23110 and via SIP/VoIP proxy 23210. In another example, emulator6423 can exchange the data with the telecommunications network via SIPgateway 24410 and via SIP/VoIP proxy 24210. In one or more embodiments,the RTP can include a packet format for delivering audio and/or videovia an IP network.

At 30090, the emulator can receive user input that indicates that thetelephone call is to be ended. In one example, emulator 6422 can receivethe user input that indicates that the telephone call is to be ended viaclient app 23230. In another example, emulator 6423 can receive the userinput that indicates that the telephone call is to be ended via clientinterface 63022.

At 30100, the emulator can provide a BYE request to thetelecommunications network. For example, a signal that indicates the BYErequest can be provided to the telecommunications network via SIP. Inone instance, emulator 6422 can provide the signal that indicates theBYE request to the telecommunications network via SIP gateway 23110 andvia SIP/VoIP proxy 23210. In another instance, emulator 6423 can providethe signal that indicates the BYE request to the telecommunicationsnetwork via SIP gateway 24410 and via SIP/VoIP proxy 24210.

At 30110, the emulator can receive an OK acknowledgement from thetelecommunications network. For example, a signal that indicates the OKacknowledgement can be received from the telecommunications network viaSIP. In one instance, emulator 6422 can receive the signal thatindicates the OK acknowledgement from the telecommunications network viaSIP gateway 23110 and via SIP/VoIP proxy 23210. In another instance,emulator 6423 can receive the signal that indicates the OKacknowledgement from the telecommunications network via SIP gateway24410 and via SIP/VoIP proxy 24210.

Turning now to FIG. 31, an exemplary method of utilizing an emulator isillustrated, according to one or more embodiments. At 31010, an emulatorcan receive, from a first user, user input associated with a networkidentification associated with an endpoint (e.g., a telephony deviceconfigured to be operated by a user, another emulator, a wirelesstelephone, a wired telephone, an auto-attendant, a conferencing system,etc.) of a telecommunications network. In one example, the user inputfrom the first user can include a selection from a contacts list and/ordatabase. For instance, each selectable element of the contacts listand/or database can be associated with at least one networkidentification associated with an endpoint of the telecommunicationsnetwork. In another example, the user input from the first user caninclude a telephone number. In one or more embodiments, the networkidentification associated with the endpoint can include one or more ofan IP addresses (e.g., an IP version 4 address, an IP version 6 address,etc.), a MAC address, an ESN, a MIN, and a MDN, among others.

At 31020, an emulator can provide, to a telecommunications network, asignal that indicates the network identification associated with theendpoint. In one or more embodiments, providing the signal thatindicates the network identification associated with the endpoint caninclude providing the signal that indicates the network identificationassociated with the endpoint via SIP. In one example, emulator 6422 canprovide the signal that indicates the network identification associatedwith the endpoint via SIP gateway 23110 and via SIP/VoIP proxy 23210,illustrated in FIG. 23. In another example, emulator 6423 can providethe signal that indicates the network identification associated with theendpoint via SIP gateway 24110 and via SIP/VoIP proxy 24210, illustratedin FIG. 24.

At 31030, the emulator can provide an invite to a telecommunicationsnetwork. In one or more embodiments, providing the invite to thetelecommunications network can include providing, to thetelecommunications network, a signal that indicates the invite via SIP.In one example, emulator 6422 can provide the signal that indicates theinvite via SIP gateway 23110 and via SIP/VoIP proxy 23210. In anotherexample, emulator 6423 can receive the signal that indicates the invitevia SIP gateway 24110 and via SIP/VoIP proxy 24210.

At 31040, the emulator can receive a signal from the telecommunicationsnetwork that indicates the endpoint is trying to summon a second user(e.g., a called party). In one or more embodiments, receiving the signalfrom the telecommunications network that indicates the endpoint istrying to summon the second user can include receiving, via SIP, thesignal from the telecommunications network that indicates the endpointis trying to summon the second user. In one example, emulator 6422 canreceive the signal that indicates the endpoint is trying to summon thesecond user via SIP gateway 23110 and via SIP/VoIP proxy 23210. Inanother example, emulator 6423 can receive the signal that indicates theendpoint is trying to summon the second user via SIP gateway 24110 andvia SIP/VoIP proxy 24210.

At 31050, the emulator can receive, from the telecommunications network,a signal that indicates that the endpoint is providing an indication ofan incoming telephone call to the second user. In one or moreembodiments, receiving the signal that indicates that the endpoint isproviding the indication of the incoming telephone call to the seconduser can include receiving the signal that indicates that the endpointis providing the indication of the incoming telephone call to the seconduser via SIP. In one example, emulator 6422 can receive the signal thatindicates that the endpoint is providing the indication of the incomingtelephone call to the second user via SIP gateway 23110 and via SIP/VoIPproxy 23210. In another example, emulator 6423 can receive the signalthat indicates that the endpoint is providing the indication of theincoming telephone call to the second user via SIP gateway 24110 and viaSIP/VoIP proxy 24210.

In one or more embodiments, the emulator can indicate, to the firstuser, that the endpoint is providing the indication of the incomingtelephone call to the second user. In one example, the emulator canindicate, to the first user, that the endpoint is providing theindication of the incoming telephone call to the second user via amessage and/or a graphic. In one instance, emulator 6422 can display, tothe first user, a message and/or a graphic that the endpoint isproviding the indication of the incoming telephone call to the seconduser via client app 23230. In another instance, emulator 6423 candisplay, to the first user, a message and/or a graphic that the endpointis providing the indication of the incoming telephone call to the seconduser via client interface 63022.

In another example, the emulator can indicate, to the first user, thatthe endpoint is providing the indication of the incoming telephone callto the second user via one or more sounds. In one instance, emulator6422 can indicate, to the first user, via a speaker associated withlocal CS 15011. In another instance, emulator 6422 can indicate, to thefirst user, via a speaker associated with CCD 1112. In one or moreembodiments, one or more sounds that indicate, to the first user, thatthe endpoint is providing the indication of the incoming telephone callto the second user can include a ring-back.

At 31060, the emulator can receive, from the telecommunications network,a signal that indicates the second user has answered. For example, thesignal that indicates the second user has answered the telephone callcan be received from the telecommunications network via SIP. In oneinstance, emulator 6422 can receive the signal that indicates the seconduser has answered the telephone call can be received from thetelecommunications network via SIP gateway 23110 and via SIP/VoIP proxy23210. In another instance, emulator 6423 can receive the signal thatindicates the second user has answered the telephone call can bereceived from the telecommunications network via SIP gateway 24410 andvia SIP/VoIP proxy 24210.

At 31070, the emulator can provide an acknowledgement to thetelecommunications network. For example, a signal that indicates theacknowledgement can be provided to the telecommunications network viaSIP. In one instance, emulator 6422 can provide the signal thatindicates the acknowledgement to the telecommunications network via SIPgateway 23110 and via SIP/VoIP proxy 23210. In another instance,emulator 6423 can provide the signal that indicates the acknowledgementto the telecommunications network via SIP gateway 24410 and via SIP/VoIPproxy 24210.

At 31080, the emulator can exchange data (e.g., RTP (real-time protocol)data) with the telecommunications network. In one example, emulator 6422can exchange the data with the telecommunications network via SIPgateway 23110 and via SIP/VoIP proxy 23210. In another example, emulator6423 can exchange the data with the telecommunications network via SIPgateway 24410 and via SIP/VoIP proxy 24210. In one or more embodiments,the RTP can include a packet format for delivering audio and/or videovia an IP network.

At 31090, the emulator can receive user input, from the first user, thatindicates that the telephone call is to be ended. In one example,emulator 6422 can receive the user input, from the first user, thatindicates that the telephone call is to be ended via client app 23230.In another example, emulator 6423 can receive the user input, from thefirst user, that indicates that the telephone call is to be ended viaclient interface 63022.

At 31100, the emulator can provide a BYE request to thetelecommunications network. For example, a signal that indicates the BYErequest can be provided to the telecommunications network via SIP. Inone instance, emulator 6422 can provide the signal that indicates theBYE request to the telecommunications network via SIP gateway 23110 andvia SIP/VoIP proxy 23210. In another instance, emulator 6423 can providethe signal that indicates the BYE request to the telecommunicationsnetwork via SIP gateway 24410 and via SIP/VoIP proxy 24210.

At 31110, the emulator can receive an OK acknowledgement from thetelecommunications network. For example, a signal that indicates the OKacknowledgement can be received from the telecommunications network viaSIP. In one instance, emulator 6422 can receive the signal thatindicates the OK acknowledgement from the telecommunications network viaSIP gateway 23110 and via SIP/VoIP proxy 23210. In another instance,emulator 6423 can receive the signal that indicates the OKacknowledgement from the telecommunications network via SIP gateway24410 and via SIP/VoIP proxy 24210.

Turning now to FIGS. 32 and 33, exemplary block diagrams of emulatorscoupled together is illustrated, according to one or more embodiments.As shown, emulator 6420 (e.g., a first emulator) can be coupled toemulator 6421 (e.g., a second emulator), and emulator 6420 (e.g., thefirst emulator) can be coupled to emulator 6422 (e.g., a thirdemulator).

In one or more embodiments, two or more devices can work and/or functiontogether. For example, the two or more devices can communicate via apersonal area network (PAN). For instance, the PAN can include one ormore of a wired network and a wireless network. In one or moreembodiments, devices of the PAN can communicate via one or more ofBluetooth (e.g., via one or more of Bluetooth basic rate, Bluetoothenhanced data rate, Bluetooth low energy, etc.), ZigBEE, NFC, wirelessUSB, wireless Ethernet, WiFi, Z-Wave, IEEE 802.11, IEEE 802.15, IEEE802.15.4, and a proprietary wireless protocol, among others. Forexample, devices of the PAN can communicate via one or more ISM(industrial, scientific and medical) bands. For instance, an ISM bandcan include a frequency range of 6.765-6.795 Mhz, 433.05-434.79 Mhz,902-928 Mhz, 2.4-2.5 Ghz, 5.725-5.875 Ghz, or 24.0-24.25 Ghz, amongothers. In one or more embodiments, devices of the PAN can communicatevia one or more of a CAN (controller area network) protocol, Flexray,SPI (serial peripheral interconnect), USB, Ethernet, IEEE 802.3,Firewire, IEEE 1394, I²C (inter-integrated circuit), Thunderbolt, and aproprietary wired protocol, among others.

In one or more embodiments, CS 5210 can emulate a PAN that couples twoor more of emulators 6420-6422. For example, one or more of emulators6420-6422 can be configured such that a first physical device, emulatedby a first emulator, can work and/or function with a second physicaldevice, emulated by a second emulator.

In one instance, illustrated in FIG. 32, a CFG 32310 of a MD 32112 canbe provided to emulator 6420; emulator 6422 can be configured with CFG5310 and coupled to emulator 6420 with CFG 32310; and one or more of CFG5310 and CD 2000 can be configured and/or can be provided to user 5010in accordance with one or more systems, methods, and/or processesdescribed herein (e.g., with reference to FIGS. 5A-5H). In anotherinstance, illustrated in FIG. 33, CFG 32310, stored via one or more ofstorages 6120-6122, can be provided to emulator 6420; emulator 6422 canbe configured with CFG 5310 and coupled to emulator 6420 with CFG 32310;and one or more of CFG 5310 and CD 2000 can be configured and/or can beprovided to user 5010 in accordance with one or more systems, methods,and/or processes described herein (e.g., with reference to FIGS. 5A-5H).

Turning now to FIG. 34, an exemplary method of emulating two or morecoupled mobile devices is illustrated, according to one or moreembodiments. At 34010, two or more physical mobile devices can beemulated. For example, two or more of emulators 6420-6425 can emulatetwo or more physical mobile devices. For instance, at least two of theemulated physical devices can be different physical devices.

At 34020, a first configuration can be received. For example, CS 5210can receive the first configuration. In one instance, the firstconfiguration can be CFG 32310, and CS 5210 can receive CFG 32310, vianetwork 1010, from MD 32310, as illustrated in FIG. 32. In anotherinstance, CS 5210 can receive CFG 32310 from at least one of storages6120-6122, as illustrated in FIG. 33.

At 34030, a first emulator of the two or more emulators can beconfigured with the first configuration. For example, the first emulatorcan be emulator 6420, and emulator 6420 can be configured with CFG32310, as illustrated in FIGS. 32 and 33. At 34040, a coupling of thefirst emulator and a second emulator can be emulated. For example, thesecond emulator can be emulator 6422, and CD 5210 can emulate a couplingof emulator 6420 with emulator 6422. In one instance, the coupling ofemulator 6420 with emulator 6422 can be an emulated wired coupling. Inanother instance, the coupling of emulator 6420 with emulator 6422 canbe an emulated wireless coupling.

At 34050, data can be received via a network. For example, CS 5210 canreceive data from user 5010 via network 1010. At 34060, the receiveddata can be provided to the second emulator. For example, the receiveddata can be provided to emulator 6422.

At 34070 a second configuration can be created. For example, thereceived data can be utilized to configure the second emulated computingdevice and/or create a second configuration (e.g., CFG 5310). Forinstance, CFG 5310 can include one or more sound recordings (e.g., MP3songs, musical pieces, voice memos, conversations, lectures, etc.), oneor more contacts (e.g., contact information associated with people,places, companies, etc.), one or more bookmarks (e.g., web browser bookmarks), one or more ebooks, one or more social networking sites'respective information (e.g., Facebook information, Twitter information,MySpace information, Foursquare information, Last.fm information,Google+ information, etc.) associated with user 5010, and/or one or moremobile device apps (e.g., smart phone apps, tablet computer apps, musicplayer apps, in-vehicle apps, etc.), among others, based on and/orcreated via the received data.

At 34080, the second configuration can be stored. In one example, thesecond configuration can be stored via storage 5121. In another example,the second configuration can be stored via one or more of storages6120-6122, illustrated in FIG. 6E. At 34090, user input indicating adelivery method can be received. In one example, CS 5210 can receive theuser input indicating the delivery method. In another example, merchantCD 5114 can receive the user input indicating the delivery method.

At 34100, a delivery method can be determined. In one example, CS 5210can determine the delivery method. In another example, merchant CD 5114can determine the delivery method. In one or more embodiments, deliveryof the second configuration can include one or more of delivering theconfiguration via the network (e.g., network 1010) and delivering aphysical computing device configured with the second configuration.

If the delivery of the second configuration (e.g., CFG 5310) includesdelivering the configuration via the network (e.g., network 1010), thesecond configuration can be provided to the user via the network, at34110. For example, CFG 5310 can be delivered to CCD 1112 and/or to MD5510 via network 1010, as illustrated in FIG. 5H. If the delivery of thesecond configuration (e.g., CFG 5310) includes delivering the physicalcomputing device configured with the second configuration, the physicalcomputing device can be configured with the second configuration, at34120, and the physical computing device (e.g., CD 2000) can be providedto a physical delivery service, at 34130. For instance, the physicaldelivery service can provide the physical computing device (e.g., CD2000) as described herein.

In one or more embodiments, the term “memory medium” can mean a“memory”, a “memory device”, and/or “tangible computer readable storagemedium”. In one example, one or more of a “memory”, a “memory device”,and “tangible computer readable storage medium” can include volatilestorage such as SRAM, DRAM, Rambus RAM, EDO RAM, random access memory,etc. In another example, one or more of a “memory”, a “memory device”,and “tangible computer readable storage medium” can include nonvolatilestorage such as a CD-ROM, a DVD-ROM, a floppy disk, a magnetic tape,EEPROM, EPROM, flash memory, NVRAM, FRAM, a magnetic media (e.g., a harddrive), optical storage, etc. In one or more embodiments, a memorymedium can include one or more volatile storages and/or one or morenonvolatile storages. In one or more embodiments, one or more of amemory medium, a memory, a memory device, and a tangible computerreadable storage medium can be or include non-transient memory and/orstorage.

In one or more embodiments, a computer system, a computing device,and/or a computer can be broadly characterized to include any devicethat includes a processor that executes instructions from a memorymedium. For example, a processor (e.g., a central processing unit orCPU) can execute instructions from a memory medium that stores theinstructions which can include one or more software programs inaccordance with one or more of methods, processes, and/or flowchartsdescribed herein. For instance, the processor and the memory medium,that stores the instructions which can include one or more softwareprograms in accordance with one or more of methods, processes, and/orflowcharts described herein, can form one or more means for one or morefunctionalities described with references to methods, processes, and/orflowcharts described herein. In one or more embodiments, a memory mediumcan be and/or can include an article of manufacture, a program product,and/or a software product. For example, the memory medium can be codedand/or encoded with instructions in accordance with one or more ofmethods, processes, and/or flowcharts described herein to produce anarticle of manufacture, a program product, and/or a software product.

One or more of the method elements described herein and/or one or moreportions of an implementation of a method element can be repeated, canbe performed in varying orders, can be performed concurrently with oneor more of the other method elements and/or one or more portions of animplementation of a method element, or can be omitted, according to oneor more embodiments. In one or more embodiments, concurrently can meansimultaneously. In one or more embodiments, concurrently can meanapparently simultaneously according to some metric. For example, twotasks can be context switched such that such that they appear to besimultaneous to a human. In one instance, a first task of the two taskscan include a first method element and/or a first portion of a firstmethod element. In a second instance, a second task of the two tasks caninclude a second method element and/or a first portion of a secondmethod element. In another instance, a second task of the two tasks caninclude the first method element and/or a second portion of the firstmethod element. Further, one or more of the system elements describedherein can be omitted and additional system elements can be added asdesired, according to one or more embodiments. Moreover, supplementary,additional, and/or duplicated method elements can be instantiated and/orperformed as desired, according to one or more embodiments.

One or more modifications and/or alternatives of the embodimentsdescribed herein may be apparent to those skilled in the art in view ofthis description. Hence, descriptions of the embodiments, describedherein, are to be taken and/or construed as illustrative and/orexemplary only and are for the purpose of teaching those skilled in theart the general manner of carrying out an invention described in theappended claims. In one or more embodiments, one or more materialsand/or elements can be swapped or substituted for those illustrated anddescribed herein. In one or more embodiments, one or more parts and/orprocesses can be reversed, and/or certain one or more features of thedescribed one or more embodiments can be utilized independently, aswould be apparent to one skilled in the art after having the benefit ofthis description.

What is claimed is:
 1. A method, comprising: concurrently emulating aplurality of emulated mobile devices, wherein each of the plurality ofemulated mobile devices corresponds to a physical mobile device, whereinat least two of the plurality of emulated mobile devices emulate twodifferent physical mobile devices, wherein a first emulated mobiledevice of the plurality of emulated mobile devices that corresponds to afirst physical mobile device of the two different physical mobiledevices includes a first physical processor, a first physical memory,and a first physical integrated circuit, wherein a second emulatedmobile device of the plurality of emulated mobile devices thatcorresponds to a second physical mobile device of the two differentphysical mobile devices includes a second physical processor, a secondphysical memory, and a second physical integrated circuit, and whereinat least one of the first physical processor, the first physical memory,and the first physical integrated circuit is different from acorresponding one of the second physical processor, the second physicalmemory, and the second physical integrated circuit; receiving a firstconfiguration; configuring the emulated first mobile device with thefirst configuration; emulating a coupling of the first mobile devicewith the second mobile device; receiving, from a user via a network,data associated with a network identifier; providing, based on thenetwork identifier, the received data to the second emulated mobiledevice; creating a second configuration based on the received data; andproviding the second configuration to the user.
 2. The method of claim1, further comprising: providing the second physical mobile device to aphysical delivery service.
 3. The method of claim 2, further comprising:configuring the second physical mobile device with the secondconfiguration.
 4. The method of claim 1, wherein emulating the couplingof the first mobile device with the second mobile device includesemulating a wireless coupling of the first mobile device with the secondmobile device.
 5. The method of claim 1, wherein emulating the couplingof the first mobile device with the second mobile device includesemulating a wired coupling of the first mobile device with the secondmobile device.
 6. The method of claim 1, wherein the secondconfiguration includes at least one of a sound recording, contactinformation, login information, online account information, a bookmark,an ebook, a social networking site information, an a mobile deviceapplication.
 7. The method of claim 1, wherein providing the secondconfiguration to the user includes providing the second configuration tothe user via the network.
 8. The method of claim 1, wherein the firstphysical integrated circuit includes at least one of a first globalpositioning system (GPS) device, a first GSM (global system for mobilecommunications) telephone network interface device, a first codedivision multiple access (CDMA) telephone network interface device, afirst graphics processing unit, a first graphics processing unit, afirst WiFi interface device, and a first Bluetooth device; and whereinthe second physical integrated circuit includes at least one of a secondGPS device, a second GSM telephone network interface device, a secondCDMA telephone network interface device, a second graphics processingunit, a second graphics processing unit, a second WiFi interface device,and a second Bluetooth device.
 9. The method of claim 1, wherein thesecond physical mobile device includes at least one of an in-vehiclecomputing device and a wearable device.
 10. A system, comprising: aprocessor; a memory coupled to the processor; a network interfacecoupled to the processor and configured to be coupled to a network;wherein the memory includes instructions that when executed by theprocessor, the system: concurrently emulates a plurality of emulatedmobile devices, wherein each of the plurality of emulated mobile devicescorresponds to a physical mobile device, wherein at least two of theplurality of emulated mobile devices emulate two different physicalmobile devices, wherein a first emulated mobile device of the pluralityof emulated mobile devices that corresponds to a first physical mobiledevice of the two different physical mobile devices includes a firstphysical processor, a first physical memory, and a first physicalintegrated circuit, wherein a second emulated mobile device of theplurality of emulated mobile devices that corresponds to a secondphysical mobile device of the two different physical mobile devicesincludes a second physical processor, a second physical memory, and asecond physical integrated circuit, and wherein at least one of thefirst physical processor, the first physical memory, and the firstphysical integrated circuit is different from a corresponding one of thesecond physical processor, the second physical memory, and the secondphysical integrated circuit; receives a first configuration; configuresthe emulated first mobile device with the first configuration; emulatesa coupling of the first mobile device with the second mobile device;receives, from a user via the network, data associated with a networkidentifier; provides, based on the network identifier, the received datato the second emulated mobile device; creates a second configurationbased on the received data; and provides the second configuration to theuser.
 11. The system of claim 10, wherein the memory further includesinstructions that when executed by the processor, the system: markspackaging of the physical mobile device with identity informationassociated with the user and physical address information associatedwith the user.
 12. The system of claim 10, wherein the memory furtherincludes instructions that when executed by the processor, the system:configures the second physical mobile device with the secondconfiguration.
 13. The system of claim 10, wherein when the systememulates the coupling of the first mobile device with the second mobiledevice, the system emulates a wireless coupling of the first mobiledevice with the second mobile device.
 14. The system of claim 10,wherein when the system emulates the coupling of the first mobile devicewith the second mobile device, the system emulates a wired coupling ofthe first mobile device with the second mobile device.
 15. The system ofclaim 10, wherein the second configuration includes at least one of asound recording, contact information, login information, online accountinformation, a bookmark, an ebook, a social networking site information,an a mobile device application.
 16. The system of claim 10, wherein whenthe system provides the second configuration to the user, the systemprovides the second configuration to the user via the network.
 17. Thesystem of claim 10, wherein the first physical integrated circuitincludes at least one of a first global positioning system (GPS) device,a first GSM (global system for mobile communications) telephone networkinterface device, a first code division multiple access (CDMA) telephonenetwork interface device, a first graphics processing unit, a firstgraphics processing unit, a first WiFi interface device, and a firstBluetooth device; and wherein the second physical integrated circuitincludes at least one of a second GPS device, a second GSM telephonenetwork interface device, a second CDMA telephone network interfacedevice, a second graphics processing unit, a second graphics processingunit, a second WiFi interface device, and a second Bluetooth device. 18.The system of claim 10, wherein the second physical mobile deviceincludes at least one of an in-vehicle computing device and a wearabledevice.
 19. A non-transient computer-readable memory device comprisinginstructions, that when the instructions are executed by a processor ofa system, the system: concurrently emulates a plurality of emulatedmobile devices, wherein each of the plurality of emulated mobile devicescorresponds to a physical mobile device, wherein at least two of theplurality of emulated mobile devices emulate two different physicalmobile devices, wherein a first emulated mobile device of the pluralityof emulated mobile devices that corresponds to a first physical mobiledevice of the two different physical mobile devices includes a firstphysical processor, a first physical memory, and a first physicalintegrated circuit, wherein a second emulated mobile device of theplurality of emulated mobile devices that corresponds to a secondphysical mobile device of the two different physical mobile devicesincludes a second physical processor, a second physical memory, and asecond physical integrated circuit, and wherein at least one of thefirst physical processor, the first physical memory, and the firstphysical integrated circuit is different from a corresponding one of thesecond physical processor, the second physical memory, and the secondphysical integrated circuit; receives a first configuration; configuresthe emulated first mobile device with the first configuration; emulatesa coupling of the first mobile device with the second mobile device;receives, from a user via the network, data associated with a networkidentifier; provides, based on the network identifier, the received datato the second emulated mobile device; creates a second configurationbased on the received data; and provides the second configuration to theuser.
 20. The non-transient computer-readable memory device of claim 19,wherein the non-transient computer-readable memory device furtherincludes instructions that when executed by the processor, the system:marks packaging of the physical mobile device with identity informationassociated with the user and physical address information associatedwith the user.
 21. The non-transient computer-readable memory device ofclaim 19, wherein the non-transient computer-readable memory devicefurther includes instructions that when executed by the processor, thesystem: configures the second physical mobile device with the secondconfiguration.
 22. The non-transient computer-readable memory device ofclaim 19, wherein when the system emulates the coupling of the firstmobile device with the second mobile device, the system emulates awireless coupling of the first mobile device with the second mobiledevice.
 23. The non-transient computer-readable memory device of claim19, wherein when the system emulates the coupling of the first mobiledevice with the second mobile device, the system emulates a wiredcoupling of the first mobile device with the second mobile device. 24.The non-transient computer-readable memory device of claim 19, whereinthe second configuration includes at least one of a sound recording,contact information, login information, online account information, abookmark, an ebook, a social networking site information, an a mobiledevice application.
 25. The non-transient computer-readable memorydevice of claim 19, wherein when the system provides the secondconfiguration to the user, the system provides the second configurationto the user via the network.
 26. The non-transient computer-readablememory device of claim 19, wherein the first physical integrated circuitincludes at least one of a first global positioning system (GPS) device,a first GSM (global system for mobile communications) telephone networkinterface device, a first code division multiple access (CDMA) telephonenetwork interface device, a first graphics processing unit, a firstgraphics processing unit, a first WiFi interface device, and a firstBluetooth device; and wherein the second physical integrated circuitincludes at least one of a second GPS device, a second GSM telephonenetwork interface device, a second CDMA telephone network interfacedevice, a second graphics processing unit, a second graphics processingunit, a second WiFi interface device, and a second Bluetooth device. 27.The non-transient computer-readable memory device of claim 19, whereinthe second physical mobile device includes at least one of an in-vehiclecomputing device and a wearable device.